sigstore-go, a Go library for Sigstore signing and verification, is susceptible to a denial of service attack in versions prior to 0.6.1 when a verifier is provided a maliciously crafted Sigstore Bundle containing large amounts of verifiable data, in the form of signed transparency log entries, RFC 3161 timestamps, and attestation subjects. The verification of these data structures is computationally expensive. This can be used to consume excessive CPU resources, leading to a denial of service attack. TUF's security model labels this type of vulnerability an "Endless data attack," and can lead to verification failing to complete and disrupting services that rely on sigstore-go for verification. This vulnerability is addressed with sigstore-go 0.6.1, which adds hard limits to the number of verifiable data structures that can be processed in a bundle. Verification will fail if a bundle has data that exceeds these limits. The limits are 32 signed transparency log entries, 32 RFC 3161 timestamps, 1024 attestation subjects, and 32 digests per attestation subject. These limits are intended to be high enough to accommodate the vast majority of use cases, while preventing the verification of maliciously crafted bundles that contain large amounts of verifiable data. Users who are vulnerable but unable to quickly upgrade may consider adding manual bundle validation to enforce limits similar to those in the referenced patch prior to calling sigstore-go's verification functions.

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

  - sigstore-go, a Go library for Sigstore signing and verification, is susceptible to a denial of service
    attack in versions prior to 0.6.1 when a verifier is provided a maliciously crafted Sigstore Bundle
    containing large amounts of verifiable data, in the form of signed transparency log entries, RFC 3161
    timestamps, and attestation subjects. The verification of these data structures is computationally
    expensive. This can be used to consume excessive CPU resources, leading to a denial of service attack.
    TUF's security model labels this type of vulnerability an "Endless data attack," and can lead to
    verification failing to complete and disrupting services that rely on sigstore-go for verification. This
    vulnerability is addressed with sigstore-go 0.6.1, which adds hard limits to the number of verifiable data
    structures that can be processed in a bundle. Verification will fail if a bundle has data that exceeds
    these limits. The limits are 32 signed transparency log entries, 32 RFC 3161 timestamps, 1024 attestation
    subjects, and 32 digests per attestation subject. These limits are intended to be high enough to
    accommodate the vast majority of use cases, while preventing the verification of maliciously crafted
    bundles that contain large amounts of verifiable data. Users who are vulnerable but unable to quickly
    upgrade may consider adding manual bundle validation to enforce limits similar to those in the referenced
    patch prior to calling sigstore-go's verification functions. (CVE-2024-45395)

ID	Name	Product	Family	Severity
414015	SCA: security update for github.com/sigstore/sigstore-go (GHSA-cq38-jh5f-37mq)	Tenable Cloud Security	SCA Checks	low
414015	SCA: security update for github.com/sigstore/sigstore-go (GHSA-cq38-jh5f-37mq)	Tenable Self-Hosted Container Security	SCA Checks	low

Detections

Analytics

CVE-2024-45395

low

Tenable Plugins

low

low