GitHub Advisoryadvisory · Go

GHSA-87x9-7grx-m28v notation-go has excessive memory allocation on verification

HIGH Published 2023-02-22 Modified 2023-02-22 Official page ↗
Aliases
CVE-2023-25656
Ecosystem
Go
Packages
github.com/notaryproject/notation-go
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses
CWE-770
Reviewed
2023-02-22

Affected packages

• Go github.com/notaryproject/notation-go: < 1.0.0-rc.3 → fixed in 1.0.0-rc.3

Description

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

Related

Alias · CVE (1)

  • CVE-2023-25656 notation-go is a collection of libraries for supporting Notation sign, verify, push, and pull of oci artifacts. vulnerability

Weakness · CWE (1)

  • CWE-770 Allocation of Resources Without Limits or Throttling weakness

References