{"answers":{"affected":"4 open source packages ship an affected version, including github.com/sigstore/cosign and cosign. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-35929 exists.","fix":"Upgrade github.com/sigstore/cosign to 1.10.1 or later.","what":"CVE-2022-35929 is a high-severity vulnerability in sigstore cosign, published on 4 Aug 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-35929 and fix it if it is affected.\n\nWhat it is: CVE-2022-35929 is a high-severity vulnerability in sigstore cosign, published on 4 Aug 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-35929 exists.\n\nAffected packages and fixed versions:\n- github.com/sigstore/cosign (Go): affected all versions; fixed in 1.10.1\n- github.com/sigstore/cosign (Go): affected all versions; fixed in 1.10.1\n- github.com/sigstore/cosign (Go): affected all versions; fixed in 1.10.1\n- cosign (Bitnami): affected all versions; fixed in 1.10.1\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-35929/ (Markdown: https://insights.sbomify.com/CVE-2022-35929/index.md)","id":"CVE-2022-35929","markdown":"https://insights.sbomify.com/CVE-2022-35929/index.md","name":"CVE-2022-35929","record":{"aliases":["BIT-cosign-2022-35929","CLEANSTART-2026-EH64058","GHSA-vjxv-45g9-9296","GO-2022-0758","SUSE-SU-2022:2877-1","openSUSE-SU-2024:12240-1"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Container signing utility","requires_auth":"low_privilege","summary":"Attackers can bypass signature verification for specific attestation types, allowing unsigned or malicious container images to appear verified.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cosign","vendor":"sigstore"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"cosign is a container signing and verification utility. In versions prior to 1.10.1 cosign can report a false positive if any attestation exists. `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 and 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. This vulnerability can be reproduced with the `distroless.dev/static@sha256:dd7614b5a12bc4d617b223c588b4e0c833402b8f4991fb5702ea83afad1986e2` image. This image has a `vuln` attestation but not an `spdx` attestation. However, if you run `cosign verify-attestation --type=spdx` on this image, it incorrectly succeeds. This issue has been addressed in version 1.10.1 of cosign. Users are advised to upgrade. There are no known workarounds for this issue.","ecosystems":["Bitnami","Go","SUSE:Linux Enterprise Module for Basesystem 15 SP4","openSUSE:Leap 15.4","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"False positive signature verification in cosign","id":"CVE-2022-35929","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":7,"n_references":2,"next":{"headline":"Ability to bypass attestation verification in sigstore PolicyController","id":"CVE-2022-35930"},"packages":[{"ecosystem":"Bitnami","fixed":["1.10.1"],"introduced":["0"],"last_affected":[],"package":"cosign","purl":"pkg:bitnami/cosign","source":"BIT-cosign-2022-35929"},{"ecosystem":"Go","fixed":["1.10.1"],"introduced":["0"],"last_affected":[],"package":"github.com/sigstore/cosign","purl":null,"source":"GHSA-vjxv-45g9-9296"},{"ecosystem":"Go","fixed":["1.10.1"],"introduced":["0"],"last_affected":[],"package":"github.com/sigstore/cosign","purl":"pkg:golang/github.com/sigstore/cosign","source":"GHSA-vjxv-45g9-9296"},{"ecosystem":"Go","fixed":["1.10.1"],"introduced":["0"],"last_affected":[],"package":"github.com/sigstore/cosign","purl":"pkg:golang/github.com/sigstore/cosign","source":"GO-2022-0758"},{"ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP4","fixed":["1.10.1-150400.3.3.1"],"introduced":["0"],"last_affected":[],"package":"cosign","purl":"pkg:rpm/suse/cosign\u0026distro=SUSE%20Linux%20Enterprise%20Module%20for%20Basesystem%2015%20SP4","source":"SUSE-SU-2022:2877-1"},{"ecosystem":"openSUSE:Leap 15.4","fixed":["1.10.1-150400.3.3.1"],"introduced":["0"],"last_affected":[],"package":"cosign","purl":"pkg:rpm/opensuse/cosign\u0026distro=openSUSE%20Leap%2015.4","source":"SUSE-SU-2022:2877-1"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["1.10.1-1.1"],"introduced":["0"],"last_affected":[],"package":"cosign","purl":"pkg:rpm/opensuse/cosign\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:12240-1"}],"prev":{"headline":"AES Crypt for Linux Password Security Vulnerability","id":"CVE-2022-35928"},"products":["cosign"],"published":"2022-08-04","related":[{"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":"SUSE"},{"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["sigstore"]},"summary":"Attackers can bypass signature verification for specific attestation types, allowing unsigned or malicious container images to appear verified.","url":"https://insights.sbomify.com/CVE-2022-35929/"}