CVE-2017-9230: Weak RNG
DISPUTED 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 Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-9230?
The severity of CVE-2017-9230 is currently disputed, and its impact can vary based on implementation.
How does CVE-2017-9230 affect Bitcoin users?
CVE-2017-9230 exposes Bitcoin users to potential manipulation of the mining process, affecting block verification.
Can CVE-2017-9230 be exploited successfully?
The exploitation of CVE-2017-9230 remains theoretical, and there is no confirmed practical exploitation as of now.
How do I mitigate risks associated with CVE-2017-9230?
To mitigate risks from CVE-2017-9230, users should ensure they are running the latest version of Bitcoin software with applicable updates.
Is there a patch available for CVE-2017-9230?
As of now, there is no specific patch addressing CVE-2017-9230 directly, but general updates may address related concerns.