CVE-2017-9230
What it is
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
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure.
- Exploit odds
- 3.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 3.3% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 3.3% · EPSS, next 30 days
- Weakness
- CWE-338
- Record status
- Modified
Affected
- Bitcoin
Attack profile CVSS 3.1 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-9230.md and follow it. Check whether this project is affected by CVE-2017-9230. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- http://www.mit.edu/~jlrubin//public/pdfs/Asicboost.pdf
- http://www.securityfocus.com/bid/98657
- https://arxiv.org/ftp/arxiv/papers/1604/1604.00575.pdf
- https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/013996.html
- https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014349.html
- https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014351.html
- https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014352.html
- http://www.mit.edu/~jlrubin//public/pdfs/Asicboost.pdf
- http://www.securityfocus.com/bid/98657
- https://arxiv.org/ftp/arxiv/papers/1604/1604.00575.pdf
- https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/013996.html
- https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014349.html
- https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014351.html
- https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014352.html