{"answers":{"affected":"4 open source packages ship an affected version, including github.com/sigstore/cosign and cosign. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-23649 in the wild and no public exploit code.","fix":"Upgrade github.com/sigstore/cosign to 1.5.2 or later.","what":"CVE-2022-23649 is a low-severity vulnerability in sigstore cosign, published on 18 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-23649 and fix it if it is affected.\n\nWhat it is: CVE-2022-23649 is a low-severity vulnerability in sigstore cosign, published on 18 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-23649 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/sigstore/cosign (Go): affected all versions; fixed in 1.5.2\n- github.com/sigstore/cosign (Go): affected all versions; fixed in 1.5.2\n- github.com/sigstore/cosign (Go): affected all versions; fixed in 1.5.2\n- cosign (Bitnami): affected all versions; fixed in 1.5.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-23649/ (Markdown: https://insights.sbomify.com/CVE-2022-23649/index.md)","id":"CVE-2022-23649","markdown":"https://insights.sbomify.com/CVE-2022-23649/index.md","name":"CVE-2022-23649","record":{"aliases":["BIT-cosign-2022-23649","CLEANSTART-2026-QF47090","GHSA-ccxc-vr6p-4858","GO-2022-0326","openSUSE-SU-2024:11860-1"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Container signing tool","requires_auth":"low_privilege","summary":"Attackers with OCI permissions can bypass Rekor transparency log verification, falsely claiming signatures are logged when they are not.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cosign","vendor":"sigstore"}],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"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.","ecosystems":["Bitnami","Go","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Certificate Validation in Cosign","id":"CVE-2022-23649","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":5,"n_references":2,"next":{"headline":"Use of Hard-coded Cryptographic Key in Netmaker","id":"CVE-2022-23650"},"packages":[{"ecosystem":"Bitnami","fixed":["1.5.2"],"introduced":["0"],"last_affected":[],"package":"cosign","purl":"pkg:bitnami/cosign","source":"BIT-cosign-2022-23649"},{"ecosystem":"Go","fixed":["1.5.2"],"introduced":["0"],"last_affected":[],"package":"github.com/sigstore/cosign","purl":null,"source":"GHSA-ccxc-vr6p-4858"},{"ecosystem":"Go","fixed":["1.5.2"],"introduced":["0"],"last_affected":[],"package":"github.com/sigstore/cosign","purl":"pkg:golang/github.com/sigstore/cosign","source":"GHSA-ccxc-vr6p-4858"},{"ecosystem":"Go","fixed":["1.5.2"],"introduced":["0"],"last_affected":[],"package":"github.com/sigstore/cosign","purl":"pkg:golang/github.com/sigstore/cosign","source":"GO-2022-0326"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["1.5.2-1.1"],"introduced":["0"],"last_affected":[],"package":"cosign","purl":"pkg:rpm/opensuse/cosign\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:11860-1"}],"prev":{"headline":"Insecure handling of image volumes in containerd CRI plugin","id":"CVE-2022-23648"},"products":["cosign"],"published":"2022-02-18","related":[{"cvss_score":7.1,"headline":"False positive signature verification in cosign","id":"CVE-2022-35929","kev_date_added":null,"published":"2022-08-04"},{"cvss_score":5.5,"headline":"Cosign verification accepts any valid Rekor entry under certain conditions","id":"CVE-2026-22703","kev_date_added":null,"published":"2026-01-10"},{"cvss_score":5.5,"headline":"Vulnerabilities with blob verification in sigstore cosign","id":"CVE-2022-36056","kev_date_added":null,"published":"2022-09-14"},{"cvss_score":4.3,"headline":"Cosign's verify-blob-attestation reports false positive when payload parsing fails","id":"CVE-2026-39395","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":4.2,"headline":"Cosign vulnerable to system-wide denial of service via malicious attachments","id":"CVE-2024-29902","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":4.2,"headline":"Cosign vulnerable to machine-wide denial of service via malicious artifacts","id":"CVE-2024-29903","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":3.7,"headline":"Cosign Certificate Chain Expiry Validation Issue Allows Issuing Certificate Expiry to Be Overlooked","id":"CVE-2026-24122","kev_date_added":null,"published":"2026-02-19"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["sigstore"]},"summary":"Attackers with OCI permissions can bypass Rekor transparency log verification, falsely claiming signatures are logged when they are not.","url":"https://insights.sbomify.com/CVE-2022-23649/"}