CVE-2023-25656High· 7.5▾ Twilightnotation-go has excessive memory allocation on verification
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 41.3 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.4%
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.
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.
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
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.
github.com/notaryproject/notation-go < 1.0.0-rc.3Upgrade to a patched release:
github.com/notaryproject/notation-go 1.0.0-rc.3Connected by shared product, vendor, weakness, or advisory.
CVE-2024-56138Medium· 4.0notation-go's timestamp signature generation lacks certificate revocation check
CVE-2024-23332Medium· 4.0Go package github.com/notaryproject/notation configured with permissive trust policies potentially susceptible to rollback attack from co…