Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

Memory leaks in code encrypting and verifying RSA payloads

CVE-2024-1394GHSA-78hx-gp6g-7mj6

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/golang-fips/openssl/v2

    Affected
    <= 2.0.0
    Fixed in
    2.0.1

  • Go github.com/microsoft/go-crypto-openssl

    Affected
    <= 0.2.8
    Fixed in
    no fixed version recorded

  • Go github.com/microsoft/go-crypto-openssl/openssl

    Affected
    <= 0.2.8
    Fixed in
    0.2.9

  • Go github.com/golang-fips/go

    Affected
    <= 1.22.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2024-1394: 1.53% estimated exploitation activity in the next 30 days; percentile 74.83 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Using crafted public RSA keys which are not compliant with SP 800-56B can cause a small memory leak when encrypting and verifying payloads. An attacker can leverage this flaw to gradually erode available memory to the point where the host crashes for lack of resources. Upon restart the attacker would have to begin again, but nevertheless there is the potential to deny service.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-78hx-gp6g-7mj6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-1394

Advisory: Memory leaks in code encrypting and verifying RSA payloads
IDs: CVE-2024-1394, GHSA-78hx-gp6g-7mj6
Record: https://patchnext.com/advisories/cve-2024-1394 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/golang-fips/openssl/v2 2.0.1; github.com/microsoft/go-crypto-openssl/openssl 0.2.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/golang-fips/openssl/v2: affected <= 2.0.0; fixed in 2.0.1
- Go github.com/microsoft/go-crypto-openssl: affected <= 0.2.8
- Go github.com/microsoft/go-crypto-openssl/openssl: affected <= 0.2.8; fixed in 0.2.9
- Go github.com/golang-fips/go: affected <= 1.22.1

## Suggested inspection (read-only)
- Go github.com/golang-fips/openssl/v2: check the installed version with your package manager.
- Go github.com/microsoft/go-crypto-openssl: check the installed version with your package manager.
- Go github.com/microsoft/go-crypto-openssl/openssl: check the installed version with your package manager.
- Go github.com/golang-fips/go: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/golang-fips/openssl/v2, github.com/microsoft/go-crypto-openssl, github.com/microsoft/go-crypto-openssl/openssl, github.com/golang-fips/go.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-78hx-gp6g-7mj6 (GitHub-reviewed advisory GHSA-78hx-gp6g-7mj6 lists affected ranges: Go github.com/golang-fips/go >=0 =0 =0 =0 <=0.2.8)

Commands are suggestions: review each one before running it.

Loading voting…