| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/sigstore/cosign | ≥ 3.0.0, < 3.0.6< 2.6.3all versions | 3.0.62.6.3 |
| github.com/sigstore/cosign/v2 | < 2.6.3 | 2.6.3 |
| github.com/sigstore/cosign/v3 | ≥ 3.0.0, < 3.0.6 | 3.0.6 |
| cosign | ≥ 3.0.0, < 3.0.6< 2.6.3 | 3.0.62.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.
When cosign verify-blob-attestation is used without --check-claims set to true, an attestation that has a valid signature but a malformed or unparsable payload would be incorrectly validated. Additionally, systems relying on --type <predicate type> to reject attestations with mismatched types would be lead to trust the unexpected attestation type.
v3.0.6, v2.6.3
Always set --check-claims=true for attestation verification.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free