Advisory

GHSA-87x9-7grx-m28v

Also known as: CVE-2023-25656, GO-2023-1589

Summary

notation-go has excessive memory allocation on verification

Details

Impact

notation-go users will find their application using excessive memory when verifying signatures and the application will be finally killed, and thus availability is impacted.

Patches

The problem has been patched in the release v1.0.0-rc.3. Users should upgrade their notation-go packages to v1.0.0-rc.3 or above.

Workarounds

Users can review their own trust policy file and check if the identity string contains =#. Meanwhile, users should only put trusted certificates in their trust stores referenced by their own trust policy files, and make sure the authenticity validation is set to enforce

Credits

The notation-go project would like to thank Adam Korczynski (@AdamKorcz) for responsibly disclosing this issue during a security fuzzing audit sponsored by CNCF and Shiwei Zhang (@shizhMSFT) for root cause analysis and detailed vulnerability report.

References

Severity

High Basis: The source's own band: HIGH

Dates

Published
2023-02-22 00:03 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

github.com/notaryproject/notation-go

Go · All systems

Affected

  • introduced 0, fixed 1.0.0-rc.3 (semver)

Fixed versions

1.0.0-rc.3

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences