CVE-2022-23649

Source
https://nvd.nist.gov/vuln/detail/CVE-2022-23649
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-23649.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2022-23649
Aliases
Related
Published
2022-02-18T22:15:12Z
Modified
2025-01-08T14:06:06.362664Z
Severity
  • 3.3 (Low) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N CVSS Calculator
Summary
[none]
Details

Cosign provides container signing, verification, and storage in an OCI registry for the sigstore project. Prior to version 1.5.2, Cosign can be manipulated to claim that an entry for a signature exists in the Rekor transparency log even if it doesn't. This requires the attacker to have pull and push permissions for the signature in OCI. This can happen with both standard signing with a keypair and "keyless signing" with Fulcio. If an attacker has access to the signature in OCI, they can manipulate cosign into believing the entry was stored in Rekor even though it wasn't. The vulnerability has been patched in v1.5.2 of Cosign. The signature in the signedEntryTimestamp provided by Rekor is now compared to the signature that is being verified. If these don't match, then an error is returned. If a valid bundle is copied to a different signature, verification should fail. Cosign output now only informs the user that certificates were verified if a certificate was in fact verified. There is currently no known workaround.

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
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.2.0
v1.2.1
v1.3.0
v1.3.1
v1.4.0
v1.4.1
v1.5.0
v1.5.1