Cosign's verify-blob-attestation reports false positive when payload parsing fails
sigstore cosign
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/sigstore/cosign/v3 Go |
|
|
| github.com/sigstore/cosign/v2 Go |
|
|
| github.com/sigstore/cosign Go |
sigstore cosign
| Product | Affected | Fixed in |
|---|---|---|
| github.com/sigstore/cosign/v3 Go |
|
|
| github.com/sigstore/cosign/v2 Go |
|
|
| github.com/sigstore/cosign Go |
|
| No fix yet |
Cosign provides code signing and transparency for containers and binaries. Prior to 3.0.6 and 2.6.3, cosign verify-blob-attestation may erroneously report a "Verified OK" result for attestations with malformed payloads or mismatched predicate types. For old-format bundles and detached signatures, this was due to a logic flaw in the error handling of the predicate type validation. For new-format bundles, the predicate type validation was bypassed completely. This vulnerability is fixed in 3.0.6 and 2.6.3.
From the CVE record · GitHub_M
Cosign's verify-blob-attestation may report “Verified OK” for attestations with malformed payloads or mismatched predicate types. This can happen when verifying old-format bundles or detached signatures because of an error-handling flaw, or new-format bundles because predicate type validation is bypassed.
Check users of Go packages github.com/sigstore/cosign/v3 versions >=3.0.0 and <3.0.6, github.com/sigstore/cosign/v2 versions <2.6.3, and all versions of github.com/sigstore/cosign through 1.13.6.