CVE-2022-23649
Last modified
CVE-2022-23649 is a low-severity vulnerability rated 3.3/10 on the CVSS scale. 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. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Sigstore | Cosign | < 1.5.2 |
References
- https://github.com/sigstore/cosign/commit/96d410a6580e4e81d24d112a0855c70ca3fb5b49Patch, Third Party Advisory
- https://github.com/sigstore/cosign/security/advisories/GHSA-ccxc-vr6p-4858Third Party Advisory
- https://github.com/sigstore/cosign/commit/96d410a6580e4e81d24d112a0855c70ca3fb5b49Patch, Third Party Advisory
- https://github.com/sigstore/cosign/security/advisories/GHSA-ccxc-vr6p-4858Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-23649?
How severe is CVE-2022-23649?
How do I fix CVE-2022-23649?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-23643Sourcegraph is a code search and navigation engine. Sourcegr…6.5
- CVE-2022-23644BookWyrm is a decentralized social network for tracking read…8.8
- CVE-2022-23645swtpm is a libtpms-based TPM emulator with socket, character…5.5
- CVE-2022-23646Next.js is a React framework. Starting with version 10.0.0 a…7.5
- CVE-2022-23647Prism is a syntax highlighting library. Starting with versio…6.1
- CVE-2022-23648containerd is a container runtime available as a daemon for …7.5
- CVE-2022-2365Cross-site Scripting (XSS) - Stored in GitHub repository zad…5.4
- CVE-2022-23650Netmaker is a platform for creating and managing virtual ove…8.8
- CVE-2022-23651b2-sdk-python is a python library to access cloud storage pr…4.7
- CVE-2022-23652capsule-proxy is a reverse proxy for Capsule Operator which …8.8
- CVE-2022-23653B2 Command Line Tool is the official command line tool for t…4.7
- CVE-2022-23654Wiki.js is a wiki app built on Node.js. In affected versions…6.5
Are you affected by CVE-2022-23649?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
