{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-9230 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-9230 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-9230 is a high-severity vulnerability in n/a, published on 24 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-9230 and fix it if it is affected.\n\nWhat it is: CVE-2017-9230 is a high-severity vulnerability in n/a, published on 24 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-9230 in the wild and no public exploit code.\n\nAffected product: n/a. 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-9230/ (Markdown: https://insights.sbomify.com/CVE-2017-9230/index.md)","id":"CVE-2017-9230","markdown":"https://insights.sbomify.com/CVE-2017-9230/index.md","name":"CVE-2017-9230","record":{"aliases":["GHSA-hx58-x97g-cc9p"],"analysis":{"component_type":"other","fix_type":"no_fix_stated","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitcoin PoW algorithm","requires_auth":"none","summary":"A theoretical weakness in Bitcoin's Proof-of-Work algorithm allows optimized mining, though it is widely considered a benign optimization rather than a security vulnerability.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bitcoin","vendor":"bitcoin"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"The Bitcoin Proof-of-Work algorithm does not consider a certain attack methodology related to 80-byte block headers with a variety of initial 64-byte chunks followed by the same 16-byte chunk, multiple candidate root values ending with the same 4 bytes, and calculations involving sqrt numbers. This violates the security assumptions of (1) the choice of input, outside of the dedicated nonce area, fed into the Proof-of-Work function should not change its difficulty to evaluate and (2) every Proof-of-Work function execution should be independent. NOTE: a number of persons feel that this methodology is a benign mining optimization, not a 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":null,"headline":"Other in n/a","id":"CVE-2017-9230","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2017"},"n_packages":0,"n_references":7,"next":{"headline":"XML external entity in n/a","id":"CVE-2017-9231"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2017-9229"},"products":["n/a"],"published":"2017-05-24","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2021-3401","kev_date_added":null,"published":"2021-02-04"},{"cvss_score":6.5,"headline":"Business logic in n/a","id":"CVE-2021-31876","kev_date_added":null,"published":"2021-05-13"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"A theoretical weakness in Bitcoin's Proof-of-Work algorithm allows optimized mining, though it is widely considered a benign optimization rather than a security vulnerability.","url":"https://insights.sbomify.com/CVE-2017-9230/"}