GHSA-vjxv-45g9-9296
cosign's `cosign verify-attestaton --type` can report a false positive if any attestation exists
En bref
- Publiée
- Mise à jour
- CVE
- CVE-2022-35929
- Alias
- BIT-cosign-2022-35929, GO-2022-0758
- CVSS_V3
- CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
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.
Paquets affectés
| Paquet | Versions |
|---|---|
| Go · github.com/sigstore/cosign | introduced 0, fixed 1.10.1 |
Références
- https://github.com/sigstore/cosign/security/advisories/GHSA-vjxv-45g9-9296 WEB
- https://nvd.nist.gov/vuln/detail/CVE-2022-35929 ADVISORY
- https://github.com/sigstore/cosign/commit/c5fda01a8ff33ca981f45a9f13e7fb6bd2080b94 WEB
- https://github.com/sigstore/cosign PACKAGE
Sources
| Source | Licence |
|---|---|
| OSV.dev | CC-BY 4.0 — GitHub Advisory Database |