CVE-2024-29903: GO-2024-2719 - Cosign malicious artifacts can cause machine-wide DoS in github.com/sigstore/cosign

CVE-2024-29903 · Severity: low · CVSS 3.1 · Published 2024-06-05

Cosign malicious artifacts can cause machine-wide DoS in github.com/sigstore/cosign

Technologies: github.com/sigstore/cosign (Go), github.com/sigstore/cosign/v2 (Go). Vendors: Go.

Quick answers

Is CVE-2024-29903 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-29903 being exploited in the wild.
How severe is CVE-2024-29903?
Low severity, with a CVSS score of 3.1, published 5 June 2024.
Which products and versions are affected?
github.com/sigstore/cosign (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=2.2.3; github.com/sigstore/cosign/v2 (Go) SEMVER:introduced=0,fixed=2.2.4.
Is there a fix for CVE-2024-29903?
Yes. github.com/sigstore/cosign/v2 (Go): upgrade to 2.2.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-29903?
Check whether you run github.com/sigstore/cosign (Go) or github.com/sigstore/cosign/v2 (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/cosign/v2 (Go): upgrade to 2.2.4 or later
    go get github.com/sigstore/cosign/v2@v2.2.4

Affected products

  • github.com/sigstore/cosign (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=2.2.3
  • github.com/sigstore/cosign/v2 (Go) SEMVER:introduced=0,fixed=2.2.4

Identifiers

  • CVE-2024-29903
  • GHSA-95pr-fxf5-86gv
  • GO-2024-2719

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