CVE-2023-25656

{"id": "CVE-2023-25656", "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}, {"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "published": "2023-02-20T16:15:10.747", "references": [{"url": "https://github.com/notaryproject/notation-go/releases/tag/v1.0.0-rc.3", "tags": ["Release Notes"], "source": "security-advisories@github.com"}, {"url": "https://github.com/notaryproject/notation-go/security/advisories/GHSA-87x9-7grx-m28v", "tags": ["Vendor Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-770"}]}, {"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-770"}]}], "descriptions": [{"lang": "en", "value": "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`."}], "lastModified": "2024-02-29T21:18:28.590", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:notaryproject:notation-go:0.7.0:alpha1:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "4FE9F3CB-8113-43F6-B85E-901E0F742EBD"}, {"criteria": "cpe:2.3:a:notaryproject:notation-go:0.8.0:alpha1:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "26950002-B9F0-42DE-95D9-AC4A4AA16693"}, {"criteria": "cpe:2.3:a:notaryproject:notation-go:0.9.0:alpha1:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "17AF7E20-1C25-4660-9F8F-D99AB3AE4B7F"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}