CVE-2022-36056

See a problem?
Source
https://nvd.nist.gov/vuln/detail/CVE-2022-36056
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-36056.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2022-36056
Aliases
Published
2022-09-14T20:15:09Z
Modified
2024-05-14T12:08:54.016786Z
Severity
  • 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N CVSS Calculator
Summary
[none]
Details

Cosign is a project under the sigstore organization which aims to make signatures invisible infrastructure. In versions prior to 1.12.0 a number of vulnerabilities have been found in cosign verify-blob, where Cosign would successfully verify an artifact when verification should have failed. First a cosign bundle can be crafted to successfully verify a blob even if the embedded rekorBundle does not reference the given signature. Second, when providing identity flags, the email and issuer of a certificate is not checked when verifying a Rekor bundle, and the GitHub Actions identity is never checked. Third, providing an invalid Rekor bundle without the experimental flag results in a successful verification. And fourth an invalid transparency log entry will result in immediate success for verification. Details and examples of these issues can be seen in the GHSA-8gw7-4j42-w388 advisory linked. Users are advised to upgrade to 1.12.0. There are no known workarounds for these issues.

References

Affected packages

Git / github.com/sigstore/cosign

Affected ranges

Type
GIT
Repo
https://github.com/sigstore/cosign
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed

Affected versions

cosigned-v0.*

cosigned-v0.0.1-dev
cosigned-v0.0.2-dev
cosigned-v0.0.3-dev

v0.*

v0.1.0
v0.2.0
v0.3.0
v0.3.1
v0.4.0
v0.5.0
v0.6.0

v1.*

v1.0.0
v1.0.1
v1.1.0
v1.10.0
v1.10.0-rc.1
v1.10.1
v1.11.0
v1.11.1
v1.2.0
v1.2.1
v1.3.0
v1.3.1
v1.4.0
v1.4.1
v1.5.0
v1.5.1
v1.6.0
v1.7.0
v1.7.1
v1.7.2
v1.8.0
v1.9.0