Vulnerability in Bitcoin
CVE-2017-9230
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
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS 0.033, 88.5th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (ARPSyndicate/cvemon, uvhw/conchimgiangnang). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- arxiv.org/ftp/arxiv/papers/1604/1604.00575.pdf (Technical Description)
- lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/013996.html (Technical Description, Mailing List, Third Party Advisory)
- lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014351.html (Mailing List, Third Party Advisory)
- www.securityfocus.com/bid/98657 (Third Party Advisory, VDB Entry, vdb-entry)
- lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014352.html (Mailing List, Third Party Advisory)
- lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014349.html (Mailing List, Third Party Advisory)
- www.mit.edu/~jlrubin//public/pdfs/Asicboost.pdf (Technical Description)