{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-20180 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-20180 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-20180 is a medium-severity vulnerability in libzerocoin, published on 6 Mar 2023. 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-2017-20180 and fix it if it is affected.\n\nWhat it is: CVE-2017-20180 is a medium-severity vulnerability in libzerocoin, published on 6 Mar 2023. 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-2017-20180 in the wild and no public exploit code.\n\nAffected product: libzerocoin. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2017-20180/ (Markdown: https://insights.sbomify.com/CVE-2017-20180/index.md)","id":"CVE-2017-20180","markdown":"https://insights.sbomify.com/CVE-2017-20180/index.md","name":"CVE-2017-20180","record":{"aliases":["GHSA-jhmf-6w7j-g482"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Zerocoin library","requires_auth":"low_privilege","summary":"Insufficient verification of data authenticity in the CoinSpend function allows bypassing proof validation in the Zerocoin library.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"libzerocoin","vendor":"zerocoin"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"A vulnerability classified as critical has been found in Zerocoin libzerocoin. Affected is the function CoinSpend::CoinSpend of the file CoinSpend.cpp of the component Proof Handler. The manipulation leads to insufficient verification of data authenticity. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The patch is identified as ce103a09ec079d0a0ed95475992348bed6e860de. It is recommended to apply a patch to fix this issue. VDB-222318 is the identifier assigned to this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Zerocoin libzerocoin Proof CoinSpend.cpp CoinSpend data authenticity","id":"CVE-2017-20180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2017"},"n_packages":0,"n_references":4,"next":{"headline":"hgzojer Vocable Trainer VocableTrainerProvider.java path traversal","id":"CVE-2017-20181"},"packages":[],"prev":{"headline":"InSTEDD Pollit tour_controller.rb TourController Privilege Escalation","id":"CVE-2017-20179"},"products":["libzerocoin"],"published":"2023-03-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Zerocoin"]},"summary":"Insufficient verification of data authenticity in the CoinSpend function allows bypassing proof validation in the Zerocoin library.","url":"https://insights.sbomify.com/CVE-2017-20180/"}