BIT-cosign-2022-35929

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/cosign/BIT-cosign-2022-35929.json
JSON Data
https://api.test.osv.dev/v1/vulns/BIT-cosign-2022-35929
Aliases
Published
2024-03-06T10:51:23.199Z
Modified
2024-11-27T19:40:48.342Z
Summary
[none]
Details

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.

Database specific
{
    "cpes": [
        "cpe:2.3:a:sigstore:cosign:*:*:*:*:*:*:*:*"
    ],
    "severity": "High"
}
References

Affected packages

Bitnami / cosign

Package

Name
cosign
Purl
pkg:bitnami/cosign

Severity

  • 7.1 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.10.1