Headline
GHSA-87x9-7grx-m28v: notation-go has excessive memory allocation on verification
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
- GitHub Advisory Database
- GitHub Reviewed
- CVE-2023-25656
notation-go has excessive memory allocation on verification
High severity GitHub Reviewed Published Feb 20, 2023 in notaryproject/notation-go • Updated Feb 22, 2023
Package
gomod github.com/notaryproject/notation-go (Go)
Affected versions
< 1.0.0-rc.3
Patched versions
1.0.0-rc.3
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
- Resource exhaustion attacks
References
- GHSA-87x9-7grx-m28v
- https://nvd.nist.gov/vuln/detail/CVE-2023-25656
- https://github.com/notaryproject/notation-go/releases/tag/v1.0.0-rc.3
Published by the National Vulnerability Database
Feb 20, 2023
Published to the GitHub Advisory Database
Feb 22, 2023
Last updated
Feb 22, 2023
Related news
notation-go is a collection of libraries for supporting Notation sign, verify, push, pull of oci artifacts. Prior to version 1.0.0-rc.3, 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. Some workarounds are available. 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`.