Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2024-1394

HIGHFix: golang-fips/openssl@85d31d0

CVE-2024-1394 is a high-severity (CVSS 7.5) CWE-401 vulnerability in github.com/golang-fips/go. O3 Security confirms whether CVE-2024-1394 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Golang-fips/openssl: memory leaks in code encrypting and decrypting rsa payloads

Also known asGHSA-78hx-gp6g-7mj6GO-2024-2660
Published
Mar 21, 2024
Updated
Jul 15, 2026
Affected
4 pkgs
Patched
2 / 4
Exploits
None indexed

Real-World Exposure

4 pkgs affected
🐹github.com/golang-fips/go🐹github.com/golang-fips/openssl/v2🐹github.com/microsoft/go-crypto-openssl🐹github.com/microsoft/go-crypto-openssl/openssl

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

4 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/golang-fips/goall versionsNo fix
🐹Gogithub.com/golang-fips/openssl/v2all versions2.0.1
🐹Gogithub.com/microsoft/go-crypto-opensslall versionsNo fix
🐹Gogithub.com/microsoft/go-crypto-openssl/opensslall versions0.2.9

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/golang-fips/go. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    No patched version of github.com/golang-fips/go has shipped for CVE-2024-1394 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-1394 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-1394. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 t
O3 Security · Impact-Aware SCA

Is CVE-2024-1394 in your dependencies?

O3 detects CVE-2024-1394 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.