{"id":"GO-2024-2472","revision":null,"records":[{"revision":"4a895334addf4c3ea7ce26a3ac856739","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2024-23332","aliases":[],"title":"Client configured with permissive trust policies susceptible to rollback attack in Notary Project","description":"The Notary Project is a set of specifications and tools intended to provide a cross-industry standard for securing software supply chains by using authentic container images and other OCI artifacts. An external actor with control of a compromised container registry can provide outdated versions of OCI artifacts, such as Images. This could lead artifact consumers with relaxed trust policies (such as `permissive` instead of `strict`) to potentially use artifacts with signatures that are no longer valid, making them susceptible to any exploits those artifacts may contain. In Notary Project, an artifact publisher can control the validity period of artifact by specifying signature expiry during the signing process. Using shorter signature validity periods along with processes to periodically resign artifacts, allows artifact producers to ensure that their consumers will only receive up-to-date artifacts. Artifact consumers should correspondingly use a `strict` or equivalent trust policy that enforces signature expiry. Together these steps enable use of up-to-date artifacts and safeguard against rollback attack in the event of registry compromise. The Notary Project offers various signature validation options such as `permissive`, `audit` and `skip` to support various scenarios. These scenarios includes 1) situations demanding urgent workload deployment, necessitating the bypassing of expired or revoked signatures; 2) auditing of artifacts lacking signatures without interrupting workload; and 3) skipping of verification for specific images that might have undergone validation through alternative mechanisms. Additionally, the Notary Project supports revocation to ensure the signature freshness. Artifact publishers can sign with short-lived certificates and revoke older certificates when necessary. This revocation serves as a signal to inform artifact consumers that the corresponding unexpired artifact is no longer approved by the publisher. This enables the artifact publisher to control the validity of the signature independently of their ability to manage artifacts in a compromised registry.","state":0,"publishedAt":"2024-01-19T22:19:37.013+00:00","modifiedAt":"2025-05-30T14:24:46.463+00:00","affected":[{"ecosystem":"Vendor product","name":"specifications","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"notaryproject\",\n                    \"product\": \"specifications\",\n                    \"versions\": [\n                        {\n                            \"version\": \"<= 1.0.1\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:L/A:L","score":4,"severity":"MEDIUM"}],"references":["https://github.com/notaryproject/specifications/security/advisories/GHSA-57wx-m636-g3g8","https://github.com/notaryproject/specifications/commit/cdabdd1042de2999c685fa5d422a785ded9c983a"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2024-23332","license":"CVE Program Terms of Use","key":"cve-program:CVE-2024-23332","identifiers":["CVE-2024-23332"]},"retained":false,"historicalAffected":[]},{"revision":"ee484646511f4fa5b7a8a68d1dc0dd33","observedAt":"2026-11-15T01:49:03.545+00:00","statement":{"source":"euvd","id":"EUVD-2024-0257","aliases":["CVE-2024-23332","GHSA-57wx-m636-g3g8"],"title":"The Notary Project is a set of specifications and tools intended to provide a cross-industry standard for securing software supply chains by using authentic container images and other OCI artifacts. An external actor with control of a compr…","description":"The Notary Project is a set of specifications and tools intended to provide a cross-industry standard for securing software supply chains by using authentic container images and other OCI artifacts. An external actor with control of a compromised container registry can provide outdated versions of OCI artifacts, such as Images. This could lead artifact consumers with relaxed trust policies (such as `permissive` instead of `strict`) to potentially use artifacts with signatures that are no longer valid, making them susceptible to any exploits those artifacts may contain. In Notary Project, an artifact publisher can control the validity period of artifact by specifying signature expiry during the signing process. Using shorter signature validity periods along with processes to periodically resign artifacts, allows artifact producers to ensure that their consumers will only receive up-to-date artifacts. Artifact consumers should correspondingly use a `strict` or equivalent trust policy that enforces signature expiry. Together these steps enable use of up-to-date artifacts and safeguard against rollback attack in the event of registry compromise. The Notary Project offers various signature validation options such as `permissive`, `audit` and `skip` to support various scenarios. These scenarios includes 1) situations demanding urgent workload deployment, necessitating the bypassing of expired or revoked signatures; 2) auditing of artifacts lacking signatures without interrupting workload; and 3) skipping of verification for specific images that might have undergone validation through alternative mechanisms. Additionally, the Notary Project supports revocation to ensure the signature freshness. Artifact publishers can sign with short-lived certificates and revoke older certificates when necessary. This revocation serves as a signal to inform artifact consumers that the corresponding unexpired artifact is no longer approved by the publisher. This enables the artifact publisher to control the validity of the signature independently of their ability to manage artifacts in a compromised registry.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:L/A:L","score":4,"severity":null}],"references":["https://github.com/notaryproject/specifications/security/advisories/GHSA-57wx-m636-g3g8","https://github.com/notaryproject/specifications/commit/cdabdd1042de2999c685fa5d422a785ded9c983a"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2024-0257","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Jan 19, 2024, 10:19:37 PM","dateUpdated":"May 30, 2025, 2:24:46 PM"},"relatedAdvisories":[],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2024-0257","identifiers":["EUVD-2024-0257","CVE-2024-23332","GHSA-57wx-m636-g3g8"]},"retained":false,"historicalAffected":[]},{"revision":"b751f1a7c782475d96d2890abf1bf81a","observedAt":"2026-10-24T23:17:22.571+00:00","statement":{"source":"nvd","id":"CVE-2024-23332","aliases":[],"title":"The Notary Project is a set of specifications and tools intended to provide a cross-industry standard for securing software supply chains by using authentic container images and other OCI artifacts. An external actor with control of a compr…","description":"The Notary Project is a set of specifications and tools intended to provide a cross-industry standard for securing software supply chains by using authentic container images and other OCI artifacts. An external actor with control of a compromised container registry can provide outdated versions of OCI artifacts, such as Images. This could lead artifact consumers with relaxed trust policies (such as `permissive` instead of `strict`) to potentially use artifacts with signatures that are no longer valid, making them susceptible to any exploits those artifacts may contain. In Notary Project, an artifact publisher can control the validity period of artifact by specifying signature expiry during the signing process. Using shorter signature validity periods along with processes to periodically resign artifacts, allows artifact producers to ensure that their consumers will only receive up-to-date artifacts. Artifact consumers should correspondingly use a `strict` or equivalent trust policy that enforces signature expiry. Together these steps enable use of up-to-date artifacts and safeguard against rollback attack in the event of registry compromise. The Notary Project offers various signature validation options such as `permissive`, `audit` and `skip` to support various scenarios. These scenarios includes 1) situations demanding urgent workload deployment, necessitating the bypassing of expired or revoked signatures; 2) auditing of artifacts lacking signatures without interrupting workload; and 3) skipping of verification for specific images that might have undergone validation through alternative mechanisms. Additionally, the Notary Project supports revocation to ensure the signature freshness. Artifact publishers can sign with short-lived certificates and revoke older certificates when necessary. This revocation serves as a signal to inform artifact consumers that the corresponding unexpired artifact is no longer approved by the publisher. This enables the artifact publisher to control the validity of the signature independently of their ability to manage artifacts in a compromised registry.","state":0,"publishedAt":"2024-01-19T23:15:07.93+00:00","modifiedAt":"2026-06-17T07:12:36.827+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · security-advisories@github.com · Secondary","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:L/A:L","score":4,"severity":"MEDIUM"},{"system":"CVSS 3.1 · nvd@nist.gov · Primary","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H","score":6.8,"severity":"MEDIUM"}],"references":["https://github.com/notaryproject/specifications/commit/cdabdd1042de2999c685fa5d422a785ded9c983a","https://github.com/notaryproject/specifications/security/advisories/GHSA-57wx-m636-g3g8"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2024-23332","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Modified","weaknesses":["CWE-672"],"productCriteria":["cpe:2.3:a:notaryproject:notation-go:*:*:*:*:*:*:*:*"],"sourceDates":{"published":"2024-01-19T23:15:07.930","lastModified":"2026-06-17T07:12:36.827"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2024-23332","identifiers":["CVE-2024-23332"]},"retained":false,"historicalAffected":[]},{"revision":"6ebb7afdab894fdb929afacc5164d453","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GHSA-57wx-m636-g3g8","aliases":["CVE-2024-23332","GO-2024-2472"],"title":"Go package github.com/notaryproject/notation configured with permissive trust policies potentially susceptible to rollback attack from compromised registry","description":"### Impact\nAn external actor with control of a compromised container registry can provide outdated versions of OCI artifacts, such as Images. This could lead artifact consumers with relaxed trust policies (such as `permissive` instead of `strict`) to potentially use artifacts with signatures that are no longer valid, making them susceptible to any exploits those artifacts may contain.\n\n### Mitigation\nIn Notary Project, an artifact publisher can control the validity period of artifact by specifying signature expiry during the signing process. Using shorter signature validity periods along with processes to periodically resign artifacts, allows artifact producers to ensure that their consumers will only receive up-to-date artifacts. Artifact consumers should correspondingly use a `strict` or equivalent trust policy that enforces signature expiry. Together these steps enable use of up-to-date artifacts and safeguard against rollback attack in the event of registry compromise. The Notary Project offers various signature validation options such as `permissive`, `audit` and `skip` to support various scenarios. These scenarios includes 1) situations demanding urgent workload deployment, necessitating the bypassing of expired or revoked signatures; 2) auditing of artifacts lacking signatures without interrupting workload; and 3) skipping of verification for specific images that might have undergone validation through alternative mechanisms.\n\nAdditionally, the Notary Project supports revocation to ensure the signature freshness. Artifact publishers can sign with short-lived certificates and revoke older certificates when necessary. This revocation serves as a signal to inform artifact consumers that the corresponding unexpired artifact is no longer approved by the publisher. This enables the artifact publisher to control the validity of the signature independently of their ability to manage artifacts in a compromised registry.\n\n### Credit\nThe Notary Project extends its gratitude to Justin Cappos (@JustinCappos) for responsibly disclosing the issue.\n\n_**Note:** we have updated [threat model](https://github.com/notaryproject/specifications/blob/main/threatmodels/notation-threatmodel.md) to include considerations for rollback attack.","state":0,"publishedAt":"2024-01-19T22:12:22+00:00","modifiedAt":"2026-09-10T03:50:04.7924324+00:00","affected":[{"ecosystem":"Go","name":"github.com/notaryproject/notation","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"last_affected","version":"1.0.0"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:L/A:L","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"references":["https://github.com/notaryproject/specifications/security/advisories/GHSA-57wx-m636-g3g8","https://nvd.nist.gov/vuln/detail/CVE-2024-23332","https://github.com/notaryproject/specifications/commit/cdabdd1042de2999c685fa5d422a785ded9c983a","https://github.com/notaryproject/specifications"],"sourceUrl":"https://github.com/advisories/GHSA-57wx-m636-g3g8","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-57wx-m636-g3g8","identifiers":["GHSA-57wx-m636-g3g8","CVE-2024-23332","GO-2024-2472"]},"retained":false,"historicalAffected":[]},{"revision":"c5171bba801e43eb899bb48b46a93943","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GO-2024-2472","aliases":["CVE-2024-23332","GHSA-57wx-m636-g3g8"],"title":"Go package github.com/notaryproject/notation configured with permissive trust policies potentially susceptible to rollback attack from compromised registry","description":"Go package github.com/notaryproject/notation configured with permissive trust policies potentially susceptible to rollback attack from compromised registry","state":0,"publishedAt":"2024-06-28T15:28:53+00:00","modifiedAt":"2026-07-02T16:59:26.8768132+00:00","affected":[{"ecosystem":"Go","name":"github.com/notaryproject/notation","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://github.com/notaryproject/specifications/security/advisories/GHSA-57wx-m636-g3g8","https://nvd.nist.gov/vuln/detail/CVE-2024-23332","https://github.com/notaryproject/specifications/commit/cdabdd1042de2999c685fa5d422a785ded9c983a"],"sourceUrl":"https://osv.dev/vulnerability/GO-2024-2472","license":"OSV · upstream source license applies","key":"osv:GO-2024-2472","identifiers":["GO-2024-2472","CVE-2024-23332","GHSA-57wx-m636-g3g8"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-16T18:47:10.8457019+00:00","complete":true,"records":1781,"lastAttemptAt":"2026-11-16T18:47:10.8457019+00:00","lastSuccessAt":"2026-11-16T18:47:11.0716622+00:00","error":null,"lastVerifiedAt":"2026-11-16T18:47:11.071663+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-6be044d0e08779dadd136f949a536de4047af96f5d7bceb7e190ecffbb8f18ca-7b226a5dbb956f6efa40aa530e16b552d2766bd2cfeae2c8f66152d783ec78d1","complete":true,"records":426117,"lastAttemptAt":"2026-11-16T18:44:56.949882+00:00","lastSuccessAt":"2026-11-16T18:44:56.8623544+00:00","error":null,"lastVerifiedAt":"2026-11-16T18:44:56.949882+00:00","snapshotPublishedAt":"2026-11-16T18:30:10+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-ffcf524d3cbf41d2a3a6fa937f216dd0","complete":true,"records":13830,"lastAttemptAt":"2026-11-16T18:47:40.7926227+00:00","lastSuccessAt":"2026-11-16T18:47:40.774+00:00","error":null,"lastVerifiedAt":"2026-11-16T18:47:40.774+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13883,"expectedIdentifiers":13883,"failedIdentifiers":0},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-16T18:47:10.8457019+00:00","complete":true,"records":1125,"lastAttemptAt":"2026-11-16T18:47:10.8457019+00:00","lastSuccessAt":"2026-11-16T18:47:11.0725273+00:00","error":null,"lastVerifiedAt":"2026-11-16T18:47:11.0725276+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-85ccba0af8894ad495cf1ce959f9030f","complete":false,"records":13842,"lastAttemptAt":"2026-11-16T18:47:38.4901027+00:00","lastSuccessAt":"2026-11-16T18:47:38.474+00:00","error":"209 identifier lookups failed; latest failures include HttpError (HTTP 503). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-16T18:47:38.474+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13574,"expectedIdentifiers":13883,"failedIdentifiers":209},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-64eea06dbd27de8464d5dbce1b78cc794cc59e2d901516ae0d3ea76e624cdae0","complete":true,"records":9955,"lastAttemptAt":"2026-11-16T18:47:10.7901587+00:00","lastSuccessAt":"2026-11-14T13:57:23.1208135+00:00","error":null,"lastVerifiedAt":"2026-11-16T18:47:10.7901587+00:00","snapshotPublishedAt":"2026-11-14T13:17:57+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-f4424d7d4861b1af1404bd15abcb83f295dcd003412a9340ca99dc8200aa148a","complete":true,"records":2014,"lastAttemptAt":"2026-11-16T18:44:57.0142322+00:00","lastSuccessAt":"2026-11-13T19:57:08.2864435+00:00","error":null,"lastVerifiedAt":"2026-11-16T18:44:57.0142322+00:00","snapshotPublishedAt":"2026-11-13T19:33:10+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-6086d649bcb454cdf302d7d9275177bda73550e1b6e446b3520e9b6266d3582c","complete":true,"records":3148,"lastAttemptAt":"2026-11-16T18:47:10.8068878+00:00","lastSuccessAt":"2026-11-15T11:05:17.1034234+00:00","error":null,"lastVerifiedAt":"2026-11-16T18:47:10.8068878+00:00","snapshotPublishedAt":"2026-11-15T10:03:04+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-a545a204cb7e029142fca3977ea456f4a00759bf811f31b6042225ef52bf5867","complete":true,"records":232531,"lastAttemptAt":"2026-11-16T18:47:10.4632154+00:00","lastSuccessAt":"2026-11-16T18:47:09.141739+00:00","error":null,"lastVerifiedAt":"2026-11-16T18:47:10.4632154+00:00","snapshotPublishedAt":"2026-11-16T18:33:19+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}