Ecosyste.ms: Advisories
An open API service providing security vulnerability metadata for many open source software ecosystems.
Security Advisories: GSA_kwCzR0hTQS04N3g5LTdncngtbTI4ds4AAxw4
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 Permalink: https://github.com/advisories/GHSA-87x9-7grx-m28v
JSON: https://advisories.ecosyste.ms/api/v1/advisories/GSA_kwCzR0hTQS04N3g5LTdncngtbTI4ds4AAxw4
Source: GitHub Advisory Database
Origin: Unspecified
Severity: High
Classification: General
Published: about 1 year ago
Updated: 10 months ago
CVSS Score: 7.5
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Identifiers: GHSA-87x9-7grx-m28v, CVE-2023-25656
References:
- https://github.com/notaryproject/notation-go/security/advisories/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
- https://github.com/notaryproject/notation-go/pull/275
- https://github.com/advisories/GHSA-87x9-7grx-m28v
Blast Radius: 10.6
Affected Packages
go:github.com/notaryproject/notation-go
Dependent packages: 29Dependent repositories: 26
Downloads:
Affected Version Ranges: < 1.0.0-rc.3
Fixed in: 1.0.0-rc.3
All affected versions: 1.0.0-rc.1, 1.0.0-rc.2
All unaffected versions: 1.0.0, 1.0.1, 1.1.0