Vulnerability in Sigstore Gitsign

CVE-2024-51746

Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. gitsign may select the wrong Rekor entry to use during online verification when multiple entries are returned by the log. gitsign uses Rekor's search API to fetch entries that apply to a signature being verified. The parameters used for the search are the public key and the payload. The search API returns entries that match either condition rather than both. When gitsign's credential cache is used, there can be multiple entries that use the same ephemeral keypair / signing certificate. As gitsign assumes both conditions are matched by Rekor, there is no additional validation that the entry's hash matches the payload being verified, meaning that the wrong entry can be used to successfully pass verification. Impact is minimal as while gitsign does not match the payload against the entry, it does ensure that the certificate matches. This would need to be exploited during the certificate validity window (10 minutes) by the key holder.

Published · last modified .

EPSS exploit prediction

EPSS: 0.001 (1.5th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 1st percentile — 1.5% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2024-51746: held from 0.001 to 0.001.

EPSS over last 30 days · oldest: 0.001 · newest: 0.001 · change: 0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2024-51746?
CVE-2024-51746 is a vulnerability in Sigstore Gitsign, classified under Use of Incorrectly-Resolved Name or Reference. Published 2024-11-05.
Is CVE-2024-51746 known to be exploited?
1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.