CVE-2023-25656: Github.com/notaryproject/notation go Notation-go Has Excessive Memory Allocation Vulnerability
HIGHCVE-2023-25656 is a HIGH (CVSS 7.5) notation-go has excessive memory allocation vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Github.com/notaryproject/notation go libraries in the Go ecosystem. The issue involves notation-go has excessive memory allocation on verification. Remediation is available by upgrading affected packages to version 1.0.0-rc.3.
CVE-2023-25656 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2023-25656
To remediate this vulnerability, upgrade all affected Github.com/notaryproject/notation go dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/notaryproject/notation-go to 1.0.0-rc.3Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/notaryproject/notation-goHow to Check if You Are Affected
To determine whether your application is affected by CVE-2023-25656, inspect your project dependencies for Github.com/notaryproject/notation go:
inspect dependencies for github.com/notaryproject/notation-goAnalyze the terminal output to locate any version of Github.com/notaryproject/notation go in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.0-rc.3), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Github.com/notaryproject/notation go, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2023-25656 Affected Github.com/notaryproject/notation go Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/notaryproject/notation-go
|
Go |
< 1.0.0-rc.3
|
1.0.0-rc.3
|
References
Frequently Asked Questions
What is CVE-2023-25656?
Which Github.com/notaryproject/notation go versions are affected?
What version fixes CVE-2023-25656?
Is github.com/notaryproject/notation-go affected?
What is the CVSS score of CVE-2023-25656?
What CWE is associated with CVE-2023-25656?
How can I check Go dependencies for CVE-2023-25656?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-87x9-7grx-m28v",
"modified" : "2023-02-22T00:03:49Z",
"published" : "2023-02-22T00:03:49Z",
"aliases" : [ "CVE-2023-25656" ],
"summary" : "notation-go has excessive memory allocation on verification",
"details" : "### Impact\n\n`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.\n\n### Patches\n\nThe 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.\n\n### Workarounds\n\nUsers 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`\n\n### Credits\n\nThe `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.\n\n### References\n\n- [Resource exhaustion attacks](https://en.wikipedia.org/wiki/Resource_exhaustion_attack)\n",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/notaryproject/notation-go"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.0.0-rc.3"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/notaryproject/notation-go/security/advisories/GHSA-87x9-7grx-m28v"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-25656"
}, {
"type" : "WEB",
"url" : "https://github.com/notaryproject/notation-go/pull/275"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/notaryproject/notation-go"
}, {
"type" : "WEB",
"url" : "https://github.com/notaryproject/notation-go/releases/tag/v1.0.0-rc.3"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-770" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2023-02-22T00:03:49Z",
"nvd_published_at" : "2023-02-20T16:15:00Z"
}
}