CVE-2024-51746: GO-2024-3252 - gitsign may use incorrect Rekor entries during verification in github.com/sigstore/gitsign

CVE-2024-51746 · Severity: medium · CVSS 4 · Published 2024-11-06

gitsign may use incorrect Rekor entries during verification in github.com/sigstore/gitsign

Technologies: github.com/sigstore/gitsign (Go). Vendors: Go.

Quick answers

Is CVE-2024-51746 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-51746 being exploited in the wild.
How severe is CVE-2024-51746?
Medium severity, with a CVSS score of 4, published 6 November 2024.
Which products and versions are affected?
github.com/sigstore/gitsign (Go) SEMVER:introduced=0,fixed=0.11.0.
Is there a fix for CVE-2024-51746?
Yes. github.com/sigstore/gitsign (Go): upgrade to 0.11.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-51746?
Check whether you run github.com/sigstore/gitsign (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/sigstore/gitsign (Go): upgrade to 0.11.0 or later
    go get github.com/sigstore/gitsign@v0.11.0

Affected products

  • github.com/sigstore/gitsign (Go) SEMVER:introduced=0,fixed=0.11.0

Identifiers

  • CVE-2024-51746
  • GHSA-8pmp-678w-c8xx
  • GO-2024-3252

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.