5.3

CVE-2023-46737: sigstore cosign Uncontrolled Resource Consumption

CVSS: 5.3v3.1MediumModified
AliasesSUSE-SU-2023:4870-1CGA-2qmx-wmgc-rjgcCGA-2rc2-hjm3-6vfw
Published 07-11-2023Last modified 04-09-2024

Vulnerability summary

CVE-2023-46737 is a medium (CVSS 5.3) Uncontrolled Resource Consumption vulnerability in sigstore cosign. EPSS estimates a 0.64% chance of exploitation in the next 30 days, higher than 49.7% of scored vulnerabilities. 1 public exploit is recorded.

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

Advisory lineage

Upstream 0 · Downstream 0 · Related 18

Timeline

  1. 07-11-2023
    PublishedVulnerability first disclosed.
  2. 04-09-2024
    Last modifiedVulnerability information updated.

Description

Cosign is a sigstore signing tool for OCI containers. Cosign is susceptible to a denial of service by an attacker controlled registry. An attacker who controls a remote registry can return a high number of attestations and/or signatures to Cosign and cause Cosign to enter a long loop resulting in an endless data attack. The root cause is that Cosign loops through all attestations fetched from the remote registry in pkg/cosign.FetchAttestations. The attacker needs to compromise the registry or make a request to a registry they control. When doing so, the attacker must return a high number of attestations in the response to Cosign. The result will be that the attacker can cause Cosign to go into a long or infinite loop that will prevent other users from verifying their data. In Kyvernos case, an attacker whose privileges are limited to making requests to the cluster can make a request with an image reference to their own registry, trigger the infinite loop and deny other users from completing their admission requests. Alternatively, the attacker can obtain control of the registry used by an organization and return a high number of attestations instead the expected number of attestations. The issue can be mitigated rather simply by setting a limit to the limit of attestations that Cosign will loop through. The limit does not need to be high to be within the vast majority of use cases and still prevent the endless data attack. This issue has been patched in version 2.2.1 and users are advised to upgrade.

CVSS metrics

5 scores · 5 sources · 1 version

EPSS trend

Probability

0.64%

Chance of exploitation in the next 30 days

Percentile

50%

Versus all other CVEs

30-day change

0.00 pp

From 0.64% on 20-09-2026

20-09-202620-10-2026
EPSS score
0.64%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

1 found
  • githubUnverified

    Cosign

    Maturity: poc

Weaknesses

CWE · root cause

Affected systems

Chainguard15 products
  • aactl< 0.4.12-r7
  • apko< 0.11.3-r0
  • cosign< 2.2.1-r0
  • falcoctl-fips< 0.6.2-r2
  • flux-source-controller< 1.7.3-r0
Wolfi13 products
  • aactl< 0.4.12-r7
  • apko< 0.11.3-r0
  • cosign< 2.2.1-r0
  • flux-source-controller< 1.7.3-r0
  • ko< 0.15.1-r0
Opensuse3 products
  • cosign&distro=openSUSE Leap 15.4< 2.2.1-150400.3.14.1
  • cosign&distro=openSUSE Leap 15.5< 2.2.1-150400.3.14.1
  • cosign&distro=openSUSE Tumbleweed< 2.2.1-1.1
Suse2 products
  • cosign&distro=SUSE Linux Enterprise Module for Basesystem 15 SP4< 2.2.1-150400.3.14.1
  • cosign&distro=SUSE Linux Enterprise Module for Basesystem 15 SP5< 2.2.1-150400.3.14.1
Github.com/sigstore1 product
  • cosign< 1.13.2 | All versions (No fix recorded)
Github.com/sigstore/cosign1 product
  • v2< 2.2.1
Sigstore1 product

7 vendors · 36 products

References

11 links
Show all 11 references