GitHub Advisoryadvisory · Go

GHSA-57wx-m636-g3g8 Go package github.com/notaryproject/notation configured with permissive trust policies potentially susceptible to rollback attack from compromised registry

MEDIUM Published 2024-01-19 Modified 2024-03-01 Official page ↗
Aliases
CVE-2024-23332
Ecosystem
Go
Packages
github.com/notaryproject/notation
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:L/A:L
Weaknesses
CWE-672
Reviewed
2024-01-19

Affected packages

• Go github.com/notaryproject/notation: <= 1.0.0 (no fix yet)

Description

Impact 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. Mitigation 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. Credit The Notary Project extends its gratitude to Justin Cappos (@JustinCappos) for responsibly disclosing the issue. _Note: we have updated threat model to include considerations for rollback attack.

Related

Alias · CVE (1)

  • CVE-2024-23332 The Notary Project is a set of specifications and tools intended to provide a cross-industry standard for securing software supply chains… vulnerability

Weakness · CWE (1)

  • CWE-672 Operation on a Resource after Expiration or Release weakness

References