GitHub Advisoryadvisory · Go
GHSA-vjxv-45g9-9296 cosign's `cosign verify-attestaton --type` can report a false positive if any attestation exists
HIGH
Official page ↗
- Aliases
- CVE-2022-35929
- Ecosystem
- Go
- Packages
- github.com/sigstore/cosign
- Severity
- High
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-347
- Reviewed
- 2022-08-10
Affected packages
• Go github.com/sigstore/cosign: < 1.10.1 → fixed in 1.10.1
Description
`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
• 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. Users should upgrade to cosign version 1.10.1 or greater for a patch. Currently the only workaround is to upgrade.
Related
Alias · CVE (1)
- CVE-2022-35929 cosign is a container signing and verification utility. vulnerability
Weakness · CWE (1)
- CWE-347 Improper Verification of Cryptographic Signature weakness