CVE-2022-35929 False positive signature verification in cosign
Attackers can bypass signature verification for specific attestation types, allowing unsigned or malicious container images to appear verified.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2022-35929?
CVE-2022-35929 is a high-severity vulnerability in sigstore cosign, published on 4 Aug 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
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.
Weakness: CWE-347
Which versions are affected by CVE-2022-35929?
4 open source packages ship an affected version, including github.com/sigstore/cosign and cosign. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/sigstore/cosign Go | All versions | 1.10.1 |
github.com/sigstore/cosign Go | All versions | 1.10.1 |
github.com/sigstore/cosign Go | All versions | 1.10.1 |
cosign Bitnami | All versions | 1.10.1 |
Linux distribution packages (3)
cosign SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 1.10.1-150400.3.3.1 |
cosign openSUSE:Leap 15.4 | All versions | 1.10.1-150400.3.3.1 |
cosign openSUSE:Tumbleweed | All versions | 1.10.1-1.1 |
Products include Sigstore Cosign.
How do I fix CVE-2022-35929?
Upgrade github.com/sigstore/cosign to 1.10.1 or later.
Is CVE-2022-35929 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-35929 exists.
Other vulnerabilities in sigstore cosign
- CVE-2026-22703 Cosign verification accepts any valid Rekor entry under certain conditions
- CVE-2022-36056 Vulnerabilities with blob verification in sigstore cosign
- CVE-2026-39395 Cosign's verify-blob-attestation reports false positive when payload parsing fails
- CVE-2024-29902 Cosign vulnerable to system-wide denial of service via malicious attachments
- CVE-2024-29903 Cosign vulnerable to machine-wide denial of service via malicious artifacts
Sources
Also known as BIT-cosign-2022-35929, CLEANSTART-2026-EH64058, GHSA-vjxv-45g9-9296, GO-2022-0758, SUSE-SU-2022:2877-1, openSUSE-SU-2024:12240-1.