Notary Project notation-go 0.9.0 Alpha 1
Approved changes feed: RSS · Atom
cpe:2.3:a:notaryproject:notation-go:0.9.0:alpha1:*:*:*:*:*:*
part: a version: 0.9.0 update: alpha1
| Vendor | Notaryproject (cd82ac48-cd9e-5e68-88f1-4dc71808db05) |
|---|---|
| Product | Notation Go (882d2ca5-fbfa-5719-a0c8-69b44260bf06) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/notaryproject/specifications |
purl2cpe | 2026-06-01 10:12:04.171905 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-25656 |
vulnerable | 2026-06-08 05:56:09.612795 |
notation-go has excessive memory allocation on verification
HIGH (7.5)
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`.
Published: 2023-02-20T00:00:00.000Z
Updated: 2024-11-27T16:45:09.132Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.