CVE-2024-23332 Client configured with permissive trust policies susceptible to rollback attack in Notary Project

What is CVE-2024-23332?

CVE-2024-23332 is a medium-severity vulnerability in notaryproject specifications, published on 19 Jan 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

Official 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.

Weakness: CWE-672

Which versions are affected by CVE-2024-23332?

3 open source packages ship an affected version, including github.com/notaryproject/notation. It affects 1 product.

Products include Notaryproject Notation-Go.

How do I fix CVE-2024-23332?

No fix has been published for CVE-2024-23332 yet. Limit exposure of the affected software until one is available.

Is CVE-2024-23332 being exploited?

There is no known exploitation of CVE-2024-23332 in the wild and no public exploit code.

Other vulnerabilities in notaryproject specifications

• CVE-2023-33959 Verification bypass can cause users into verifying the wrong artifact High 8.4
• CVE-2023-25656 notation-go has excessive memory allocation on verification High 7.5
• CVE-2023-33958 Default `maxSignatureAttempts` in `notation verify` enables an endless data attack in notation Medium 5.4
• CVE-2024-51491 Process crash during CRL-based revocation check on OS using separate mount point for temp Directory in notation-go Low 3.3
• CVE-2023-33957 Denial of service from high number of artifact signatures in notation Low 2.6

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-57wx-m636-g3g8, GO-2024-2472.