Vulnerabilities · 2017 · Bitcoin
CVE-2017-9230
Bitcoin vulnerability
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
Affected products
Bitcoin. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Bitcoin runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- www.securityfocus.com/bid/98657 · Third Party Advisory
- lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/013996.html · Third Party Advisory
- lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014349.html · Third Party Advisory
- lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014351.html · Third Party Advisory
- lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014352.html · Third Party Advisory
- www.mit.edu/~jlrubin//public/pdfs/Asicboost.pdf
- arxiv.org/ftp/arxiv/papers/1604/1604.00575.pdf
- nvd.nist.gov/vuln/detail/CVE-2017-9230
- cve.org/CVERecord?id=CVE-2017-9230
More vulnerabilities in Bitcoin products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.