GHSA-87x9-7grx-m28v

notation-go has excessive memory allocation on verification

Source: GitHub Advisory Database (reviewed) High CVE-2023-25656

Packages

Ecosystem	Package	Affected	Fixed in
Go	github.com/notaryproject/notation-go	< 1.0.0-rc.3	1.0.0-rc.3

Details

As written in the advisory (Markdown source, shown as plain text).

### 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](https://github.com/notaryproject/notation-go/releases/tag/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](https://en.wikipedia.org/wiki/Resource_exhaustion_attack)

References

External links from the advisory. They lead to third-party sites.