7.5

CVE-2024-45395: sigstore sigstore-go Infinite Loop

CVSS: 7.5v3.1HighAnalyzed
AliasesCGA-26f8-x95h-xvc8CGA-5hc5-8h4c-jqxhCGA-864j-68q5-85qf
Published 04-09-2024Last modified 05-09-2024

Vulnerability summary

CVE-2024-45395 is a high (CVSS 7.5) Infinite Loop vulnerability in sigstore sigstore-go. EPSS estimates a 0.47% chance of exploitation in the next 30 days, higher than 39.1% of scored vulnerabilities.

Overall risk
30/100
0100
Medium · default modelHow is this calculated?
CVSS score
7.5/10
010
High · v3.1 (NVD)
EPSS score
0.47%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 0 · Related 5

Timeline

  1. 04-09-2024
    PublishedVulnerability first disclosed.
  2. 05-09-2024
    Last modifiedVulnerability information updated.

Description

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.

CVSS metrics

6 scores · 5 sources · 2 versions

EPSS trend

Probability

0.47%

Chance of exploitation in the next 30 days

Percentile

39%

Versus all other CVEs

30-day change

0.00 pp

From 0.47% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.47%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Chainguard5 products
  • cosign< 2.4.0-r2
  • cosign-fips< 2.4.0-r2
  • gh< 2.56.0-r0
  • gh-doc< 2.56.0-r0
  • slsa-verifier< 2.6.0-r3
Wolfi4 products
  • cosign< 2.4.0-r2
  • gh< 2.56.0-r0
  • gh-doc< 2.56.0-r0
  • slsa-verifier< 2.6.0-r3
Github.com/sigstore1 product
  • sigstore-go< 0.6.1
Sigstore1 product

4 vendors · 11 products

References

8 links