CVE-2018-17144 json
Bitcoin Core 0.14.x before 0.14.3, 0.15.x before 0.15.2, and 0.16.x before 0.16.3 and Bitcoin Knots 0.14.x through 0.16.x before 0.16.3 all…
published 8y ago modified 4mo ago also EUVD-2018-8920
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.7%
- EPSS 6.7% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
Bitcoin Core 0.14.x before 0.14.3, 0.15.x before 0.15.2, and 0.16.x before 0.16.3 and Bitcoin Knots 0.14.x through 0.16.x before 0.16.3 allow a remote denial of service (application crash) exploitable by miners via duplicate input. An attacker can make bitcoind or Bitcoin-Qt crash.
Patch / fix
- bitcoin bitcoin_core 0.14.3, 0.15.2, 0.16.3
- bitcoinknots bitcoin_knots 0.16.3
- litecoin Debian 13, Debian 12 0.16.3-1
debian advisories DEBIAN-CVE-2018-17144
- bitcoin Package Hub 15 SP5, openSUSE Leap 15.5 26.0-bp155.2.3.1
opensuse advisories openSUSE-SU-2024:0052-1
- bitcoin-daemon Arch Linux 0.16.3-1
- bitcoin-qt Arch Linux 0.16.3-1
arch linux advisories AVG-766
Is CVE-2018-17144 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
6.75% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
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:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
References
-
github.com
/bitcoin/bitcoin/blob/v0.16.3/doc/release-notes.md
patch, third-party-advisory
-
github.com
/bitcoinknots/bitcoin/blob/v0.16.3.knots20180918/doc/release-notes.md
patch, third-party-advisory
-
bitcoincore.org
/en/2018/09/18/release-0.16.3/
vendor-advisory
-
en.bitcoin.it
/wiki/Common_Vulnerabilities_and_Exposures#CVE-2018-17144
third-party-advisory
-
github.com
/JinBean/CVE-Extension
third-party-advisory
Sources
- CVE List CVE-2018-17144
- NVD CVE-2018-17144
Fencer Intel 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.