Cosign provides container signing, verification, and storage in an OCI registry for the sigstore project. Prior to version 1.5.2, Cosign can be manipulated to claim that an entry for a signature exists in the Rekor transparency log even if it doesn't. This requires the attacker to have pull and push permissions for the signature in OCI. This can happen with both standard signing with a keypair and "keyless signing" with Fulcio. If an attacker has access to the signature in OCI, they can manipulate cosign into believing the entry was stored in Rekor even though it wasn't. The vulnerability has been patched in v1.5.2 of Cosign. The `signature` in the `signedEntryTimestamp` provided by Rekor is now compared to the `signature` that is being verified. If these don't match, then an error is returned. If a valid bundle is copied to a different signature, verification should fail. Cosign output now only informs the user that certificates were verified if a certificate was in fact verified. There is currently no known workaround.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - Cosign provides container signing, verification, and storage in an OCI registry for the sigstore project.
    Prior to version 1.5.2, Cosign can be manipulated to claim that an entry for a signature exists in the
    Rekor transparency log even if it doesn't. This requires the attacker to have pull and push permissions
    for the signature in OCI. This can happen with both standard signing with a keypair and "keyless signing"
    with Fulcio. If an attacker has access to the signature in OCI, they can manipulate cosign into believing
    the entry was stored in Rekor even though it wasn't. The vulnerability has been patched in v1.5.2 of
    Cosign. The `signature` in the `signedEntryTimestamp` provided by Rekor is now compared to the `signature`
    that is being verified. If these don't match, then an error is returned. If a valid bundle is copied to a
    different signature, verification should fail. Cosign output now only informs the user that certificates
    were verified if a certificate was in fact verified. There is currently no known workaround.
    (CVE-2022-23649)

ID	Name	Product	Family	Severity
413836	SCA: security update for github.com/sigstore/cosign (GHSA-ccxc-vr6p-4858)	Tenable Cloud Security	SCA Checks	low
413836	SCA: security update for github.com/sigstore/cosign (GHSA-ccxc-vr6p-4858)	Tenable Self-Hosted Container Security	SCA Checks	low
403910	Alpine: multiple cosign packages: security update to 1.5.2-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	low
403910	Alpine: multiple cosign packages: security update to 1.5.2-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	low
407744	Alpine: multiple cosign packages, multiple sget packages: security update to 1.5.1-r0 (deprecated)	Tenable Cloud Security	Alpine Linux Local Security Checks	low
407744	Alpine: multiple cosign packages, multiple sget packages: security update to 1.5.1-r0 (deprecated)	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	low

Detections

Analytics

CVE-2022-23649

low

Tenable Plugins

low

low

low

low

low

low