CVE-2023-46737: GO-2023-2181 - Denial of service attack from remote registry in github.com/sigstore/cosign

CVE-2023-46737 · Severity: low · CVSS 3.1 · Published 2023-11-09

Denial of service attack from remote registry in github.com/sigstore/cosign

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

Quick answers

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

Affected products

  • github.com/sigstore/cosign (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=1.13.2
  • github.com/sigstore/cosign/v2 (Go) SEMVER:introduced=0,fixed=2.2.1

Identifiers

  • CVE-2023-46737
  • GHSA-vfp6-jrw2-99g9
  • GO-2023-2181

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