Skip to main content
No exploitation reportedFix available

CVE-2024-1394

No exploitation reported by the sources we read.

  • Published2024-03-21
  • Fixed in0.2.9
  • WeaknessCWE-401

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs​. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects leaked are pkey​ and ctx​. That function uses named return parameters to free pkey​ and ctx​ if there is an error initializing the context or setting the different properties. All return statements related to error cases follow the "return nil, nil, fail(...)" pattern, meaning that pkey​ and ctx​ will be nil inside the deferred function that should free them.

Timeline

dates in UTC
  1. 2024-03-2113:00CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-1394?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-1394?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV
microsoft/go-crypto-openssl
BranchAffectedFixed in
0.2< 0.2.90.2.9
0.2≤ 0.2.8no fix published
golang-fips/go
BranchAffectedFixed in
1.22≤ 1.22.1no fix published
golang-fips/openssl
BranchAffectedFixed in
2.0< 2.0.12.0.1

1 more product in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • aardvark-dnsAlmaLinux:8all versions · fixed in 2:1.10.0-1.module_el8.10.0+3792+03eaed9c
  • aardvark-dnsAlmaLinux:8all versions · fixed in 2:1.10.0-1.module_el8.10.0+3858+6ad51f9f
  • aardvark-dnsAlmaLinux:8all versions · fixed in 2:1.10.0-1.module_el8.10.0+3876+e55593a8
  • buildahAlmaLinux:9all versions · fixed in 2:1.33.7-3.el9_4and 1 other package
  • buildahAlmaLinux:8all versions · fixed in 2:1.33.8-4.module_el8.10.0+3876+e55593a8and 1 other package
  • cockpit-podmanAlmaLinux:8all versions · fixed in 84.1-1.module_el8.10.0+3858+6ad51f9f
  • conmonAlmaLinux:8all versions · fixed in 3:2.1.10-1.module_el8.10.0+3845+87b84552
  • conmonAlmaLinux:8all versions · fixed in 3:2.1.10-1.module_el8.10.0+3858+6ad51f9f

49 more package ranges on OSV.dev

Vendor advisories

  • RHSA-2024:4591 Red Hat Product Security7 products fixed

    Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.16.0 security, enhancement & bug fix update

  • RHSA-2024:1574 Red Hat Product Security322 products fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.12.54 packages and security update

  • RHSA-2024:1563 Red Hat Product Security316 products fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.15.6 packages and security update

Full record on NVD

Fix

  1. Update microsoft/go-crypto-openssl to 0.2.9
  2. Vendor fix Red Hat Product Security RHSA-2024:4591 · 7 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  3. Vendor fix Red Hat Product Security RHSA-2024:1574 · 322 productsFor OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.12/release_notes/ocp-4-1…
  4. Vendor fix Red Hat Product Security RHSA-2024:1563 · 316 productsFor OpenShift Container Platform 4.15 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.15/release_notes/ocp-4-1…
  5. Workaround from the vendor Red Hat Product Security RHSA-2024:4591 · 98 productsMitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2024-03-21
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-401read 2026-10-23
  • FIRST EPSSEPSS score1.5 %2026-10-22
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2024-03-21
Last Modified
2026-10-09
NVD status
Deferred

Frequently asked questions

What is CVE-2024-1394?

A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs​. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects leaked are pkey​ and ctx​. That function uses named return parameters to free pkey​ and ctx​ if there is an error initializing the context or setting the different properties. All return statements related to error cases follow the "return nil, nil, fail(...)" pattern, meaning that pkey​ and ctx​ will be nil inside the deferred function that should free them.

Is CVE-2024-1394 actively exploited?

Active exploitation of CVE-2024-1394 has not been confirmed. Its EPSS score was 1.5% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-1394?

CVE-2024-1394 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running golang-fips/openssl? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month