CVE-2017-12842 json
Bitcoin Core before 0.14 allows an attacker to create an ostensibly valid SPV proof for a payment to a victim who uses an SPV wallet, even…
published 2020-03-16 6 y ago modified 2026-06-17 4 mo ago also EUVD-2017-4379
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
Bitcoin Core before 0.14 allows an attacker to create an ostensibly valid SPV proof for a payment to a victim who uses an SPV wallet, even if that payment did not actually occur. Completing the attack would cost more than a million dollars, and is relevant mainly only in situations where an autonomous system relies solely on an SPV proof for transactions of a greater dollar amount.
Patch / fix
- bitcoin bitcoin_core 0.14.0
Exploit prediction
2.22% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
en.bitcoin.it
/wiki/Common_Vulnerabilities_and_Exposures
vendor-advisory
-
bitslog.wordpress.com
/2018/06/09/leaf-node-weakness-in-bitcoin-merkle-tree-design/
third-party-advisory
-
lists.linuxfoundation.org
/pipermail/bitcoin-dev/2019-February/016697.html
third-party-advisory
Sources
- CVE List CVE-2017-12842
- NVD CVE-2017-12842
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.