CVE-2023-25656
"notation-go Excessive Memory Consumption Signature Verification DoS"
Description
notation-go is a collection of libraries for supporting Notation sign, verify, push, and 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. The application will be 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`.
INFO
Published Date :
Feb. 20, 2023, 4:15 p.m.
Last Modified :
Feb. 29, 2024, 9:18 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
3.6
Exploitability Score :
3.9
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2023-25656
.
URL | Resource |
---|---|
https://github.com/notaryproject/notation-go/releases/tag/v1.0.0-rc.3 | Release Notes |
https://github.com/notaryproject/notation-go/security/advisories/GHSA-87x9-7grx-m28v | Vendor Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-25656
vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-25656
vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Mar. 01, 2023
Action Type Old Value New Value Added CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Changed Reference Type https://github.com/notaryproject/notation-go/releases/tag/v1.0.0-rc.3 No Types Assigned https://github.com/notaryproject/notation-go/releases/tag/v1.0.0-rc.3 Release Notes Changed Reference Type https://github.com/notaryproject/notation-go/security/advisories/GHSA-87x9-7grx-m28v No Types Assigned https://github.com/notaryproject/notation-go/security/advisories/GHSA-87x9-7grx-m28v Vendor Advisory Added CWE NIST CWE-770 Added CPE Configuration OR *cpe:2.3:a:notation-go_project:notation-go:0.7.0:alpha1:*:*:*:*:*:* *cpe:2.3:a:notation-go_project:notation-go:0.8.0:alpha1:*:*:*:*:*:* *cpe:2.3:a:notation-go_project:notation-go:0.9.0:alpha1:*:*:*:*:*:* -
CVE Modified by [email protected]
Feb. 21, 2023
Action Type Old Value New Value Changed Description 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`. notation-go is a collection of libraries for supporting Notation sign, verify, push, and 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. The application will be 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`. Removed CVSS V3.1 GitHub, Inc. AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Added CVSS V3.1 GitHub, Inc. AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Removed CWE GitHub, Inc. CWE-400 Added CWE GitHub, Inc. CWE-770
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2023-25656
is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2023-25656
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.10 }} 0.00%
score
0.42195
percentile