{"answers":{"affected":"3 open source packages ship an affected version, including github.com/sigstore/gitsign. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-47122 in the wild and no public exploit code.","fix":"Upgrade github.com/sigstore/gitsign to 0.8.0 or later.","what":"CVE-2023-47122 is a medium-severity vulnerability in sigstore gitsign, published on 10 Nov 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-47122 and fix it if it is affected.\n\nWhat it is: CVE-2023-47122 is a medium-severity vulnerability in sigstore gitsign, published on 10 Nov 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-47122 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/sigstore/gitsign (Go): affected from 0.6.0; fixed in 0.8.0\n- github.com/sigstore/gitsign (Go): affected from 0.6.0; fixed in 0.8.0\n- github.com/sigstore/gitsign (Go): affected from 0.6.0; fixed in 0.8.0\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-2023-47122/ (Markdown: https://insights.sbomify.com/CVE-2023-47122/index.md)","id":"CVE-2023-47122","markdown":"https://insights.sbomify.com/CVE-2023-47122/index.md","name":"CVE-2023-47122","record":{"aliases":["GHSA-xvrc-2wvh-49vc","GO-2023-2332"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Git signing tool","requires_auth":"high_privilege","summary":"Attackers could trick gitsign users into trusting invalid signatures by compromising the upstream Rekor API, bypassing local TUF verification.","user_interaction":"required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gitsign","vendor":"sigstore"}],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Gitsign is software for keyless Git signing using Sigstore. In versions of gitsign starting with 0.6.0 and prior to 0.8.0, Rekor public keys were fetched via the Rekor API, instead of through the local TUF client. If the upstream Rekor server happened to be compromised, gitsign clients could potentially be tricked into trusting incorrect signatures. There is no known compromise the default public good instance (`rekor.sigstore.dev`) - anyone using this instance is unaffected. This issue was fixed in v0.8.0. No known workarounds are available.","ecosystems":["Go"],"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":"Gitsign's Rekor public keys fetched from upstream API instead of local TUF client.","id":"CVE-2023-47122","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"supply_chain","year":"2023"},"n_packages":3,"n_references":4,"next":{"headline":"iTop vulnerable to XSS vulnerability in n:n relations \"tagset\" widget","id":"CVE-2023-47123"},"packages":[{"ecosystem":"Go","fixed":["0.8.0"],"introduced":["0.6.0"],"last_affected":[],"package":"github.com/sigstore/gitsign","purl":null,"source":"GHSA-xvrc-2wvh-49vc"},{"ecosystem":"Go","fixed":["0.8.0"],"introduced":["0.6.0"],"last_affected":[],"package":"github.com/sigstore/gitsign","purl":"pkg:golang/github.com/sigstore/gitsign","source":"GHSA-xvrc-2wvh-49vc"},{"ecosystem":"Go","fixed":["0.8.0"],"introduced":["0.6.0"],"last_affected":[],"package":"github.com/sigstore/gitsign","purl":"pkg:golang/github.com/sigstore/gitsign","source":"GO-2023-2332"}],"prev":{"headline":"Discourse SSRF vulnerability in Embedding","id":"CVE-2023-47121"},"products":["gitsign"],"published":"2023-11-10","related":[],"sources":[{"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":"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":"2024-09-03","vendors":["sigstore"]},"summary":"Attackers could trick gitsign users into trusting invalid signatures by compromising the upstream Rekor API, bypassing local TUF verification.","url":"https://insights.sbomify.com/CVE-2023-47122/"}