CVE-2022-35929: False positive signature verification in cosign
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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is CVE-2022-35929?
CVE-2022-35929 is a vulnerability in cosign, a container signing and verification utility, versions prior to 1.10.1.
What is the severity of CVE-2022-35929?
CVE-2022-35929 has a severity rating of critical (9.8).
How does CVE-2022-35929 affect Sigstore Cosign?
Sigstore Cosign versions prior to 1.10.1 are affected by CVE-2022-35929.
How can I fix CVE-2022-35929 in cosign?
To fix CVE-2022-35929, upgrade cosign to version 1.10.1 or later.
Where can I find more information about CVE-2022-35929?
More information about CVE-2022-35929 can be found at the following references: [link1](https://github.com/sigstore/cosign/commit/c5fda01a8ff33ca981f45a9f13e7fb6bd2080b94), [link2](https://github.com/sigstore/cosign/security/advisories/GHSA-vjxv-45g9-9296).