{"answers":{"affected":"3 open source packages ship an affected version, including github.com/sigstore/gitsign.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51746 exists.","fix":"Upgrade github.com/sigstore/gitsign to 0.11.0 or later.","what":"CVE-2024-51746 is a low-severity vulnerability in sigstore gitsign, published on 5 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-51746 and fix it if it is affected.\n\nWhat it is: CVE-2024-51746 is a low-severity vulnerability in sigstore gitsign, published on 5 Nov 2024. It can only be exploited from the same machine or local 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-2024-51746 exists.\n\nAffected packages and fixed versions:\n- github.com/sigstore/gitsign (Go): affected all versions; fixed in 0.11.0\n- github.com/sigstore/gitsign (Go): affected all versions; fixed in 0.11.0\n- github.com/sigstore/gitsign (Go): affected all versions; fixed in 0.11.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-2024-51746/ (Markdown: https://insights.sbomify.com/CVE-2024-51746/index.md)","id":"CVE-2024-51746","markdown":"https://insights.sbomify.com/CVE-2024-51746/index.md","name":"CVE-2024-51746","record":{"aliases":["GHSA-8pmp-678w-c8xx","GO-2024-3252"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Git signing tool","requires_auth":"none","summary":"Attackers with valid ephemeral keys can bypass signature verification by exploiting incorrect Rekor entry selection during online validation.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":1.8,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-706","name":"Use of Incorrectly-Resolved Name or Reference"}],"description":"Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. gitsign may select the wrong Rekor entry to use during online verification when multiple entries are returned by the log. gitsign uses Rekor's search API to fetch entries that apply to a signature being verified. The parameters used for the search are the public key and the payload. The search API returns entries that match either condition rather than both. When gitsign's credential cache is used, there can be multiple entries that use the same ephemeral keypair / signing certificate. As gitsign assumes both conditions are matched by Rekor, there is no additional validation that the entry's hash matches the payload being verified, meaning that the wrong entry can be used to successfully pass verification. Impact is minimal as while gitsign does not match the payload against the entry, it does ensure that the certificate matches. This would need to be exploited during the certificate validity window (10 minutes) by the key holder.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Use of incorrect Rekor entries during verification in gitsign","id":"CVE-2024-51746","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"other","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"Arbitrary File Read and Delete in kanboard","id":"CVE-2024-51747"},"packages":[{"ecosystem":"Go","fixed":["0.11.0"],"introduced":["0"],"last_affected":[],"package":"github.com/sigstore/gitsign","purl":null,"source":"GHSA-8pmp-678w-c8xx"},{"ecosystem":"Go","fixed":["0.11.0"],"introduced":["0"],"last_affected":[],"package":"github.com/sigstore/gitsign","purl":"pkg:golang/github.com/sigstore/gitsign","source":"GHSA-8pmp-678w-c8xx"},{"ecosystem":"Go","fixed":["0.11.0"],"introduced":["0"],"last_affected":[],"package":"github.com/sigstore/gitsign","purl":"pkg:golang/github.com/sigstore/gitsign","source":"GO-2024-3252"}],"prev":{"headline":"Wasmtime doesn't fully sandbox all the Windows device filenames","id":"CVE-2024-51745"},"products":["gitsign"],"published":"2024-11-05","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-05","vendors":["sigstore"]},"summary":"Attackers with valid ephemeral keys can bypass signature verification by exploiting incorrect Rekor entry selection during online validation.","url":"https://insights.sbomify.com/CVE-2024-51746/"}