Skip to content
Fencer Intel
high 7.1

CVE-2022-35929 json

False positive signature verification in cosign

published 4y ago modified 2mo ago also BIT-cosign-2022-35929 , EUVD-2022-6632 , GHSA-vjxv-45g9-9296 , GO-2022-0758

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

cosign is a container signing and verification utility. In versions prior to 1.10.1 cosign can report a false positive if any attestation exists. `cosign verify-attestation` used with the `--type` flag will report a false positive verification when there is at least one attestation with a valid signature and there are NO attestations of the type being verified (--type defaults to "custom"). This can happen when signing with a standard keypair and with "keyless" signing with Fulcio. This vulnerability can be reproduced with the `distroless.dev/static@sha256:dd7614b5a12bc4d617b223c588b4e0c833402b8f4991fb5702ea83afad1986e2` image. This image has a `vuln` attestation but not an `spdx` attestation. However, if you run `cosign verify-attestation --type=spdx` on this image, it incorrectly succeeds. This issue has been addressed in version 1.10.1 of cosign. Users are advised to upgrade. There are no known workarounds for this issue.

Patch / fix

  • go github.com/sigstore/cosign 1.10.1
  • bitnami cosign 1.10.1
  • sigstore cosign 1.10.1
  • cosign SLE Module for Basesystem 15 SP4, openSUSE Leap 15.4 1.10.1-150400.3.3.1

suse advisories SUSE-SU-2022:2877-1

  • cosign openSUSE Tumbleweed 1.10.1-1.1

opensuse advisories openSUSE-SU-2024:12240-1

  • cosign Alpine 3.24, Alpine 3.23, Alpine 3.22 +6 more 1.10.1-r0

alpine advisories ALPINE-CVE-2022-35929

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-35929 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-35929 updated cvss 9.8

cosign: `cosign verify-attestation --type` can report a false positive if any attestation exists

  • Red Hat OpenShift Serverless openshift-serverless-1/client-kn-rhel8 Red Hat Advanced Cluster Security 3 advanced-cluster-security/rhacs-docs-rhel8, advanced-cluster-security/rhacs-main-rhel8, advanced-cluster-security/rhacs-roxctl-rhel8, advanced-cluster-security/rhacs-rhel8-operator
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Container Platform 4 openshift-security-profiles-operator-container
    affected: no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/sigstore/cosign/commit/c5fda01a8ff33ca981f45a9f13e7fb6bd2080b94 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/sigstore/cosign/security/advisories/GHSA-vjxv-45g9-9296 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
GitHub 3.1 7.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/sigstore/cosign
<1.10.1
1.10.1
bitnami cosign
<1.10.1
1.10.1

Affected products

  • sigstore cosign

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.