PatchTheCVECVE-2018-17145: Bitcoin Core 0.16.x before 0.16.2 and Bitcoin Knots 0.16.x before 0.16.2 allow remote denial of service via a
59
This week
HIGH 7.5REMOTEUPGRADEUPGRADEUPGRADE
CVE-2018-17145 is a high-severity flaw (CVSS 7.5) affecting bcoin, bitcoin core, bitcoin knots. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Bitcoin Core 0.16.x before 0.16.2 and Bitcoin Knots 0.16.x before 0.16.2 allow remote denial of service via a flood of multiple transaction inv messages with random hashes, aka INVDoS. NOTE: this can also affect other cryptocurrencies, e.g., if they were forked from Bitcoin Core after 2017-11-15.
Why this priority
- High severity
- EPSS top 8%: very likely to be exploited
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 4.8% (top 8%) |
| CISA exploited list | No |
| Weakness | CWE-400 |
| Published | 2020-09-10 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
bcoin bcoin UPGRADE
Affected: < 1.0.2
Fixed in: 1.0.2
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy bcoin || rpm -q bcoin || bcoin --version
2. UPGRADE to 1.0.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade bcoin
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade bcoin
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
bitcoin bitcoin core UPGRADE
Affected: >= 0.16.0 and < 0.16.2
Fixed in: 0.16.2
Safe to downgrade to: a release before 0.16.0
1. Check installed version
apt-cache policy bitcoin-core || rpm -q bitcoin-core || bitcoin-core --version
2. UPGRADE to 0.16.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade bitcoin-core
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade bitcoin-core
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.16.0 (Debian / Ubuntu)
apt-cache madison bitcoin-core
sudo apt install bitcoin-core=<VERSION_BEFORE_0.16.0>
sudo apt-mark hold bitcoin-core
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list bitcoin-core
sudo dnf downgrade bitcoin-core-<VERSION_BEFORE_0.16.0>
sudo dnf versionlock add bitcoin-core
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
bitcoinknots bitcoin knots UPGRADE
Affected: >= 0.16.0 and < 0.16.2
Fixed in: 0.16.2
Safe to downgrade to: a release before 0.16.0
1. Check installed version
apt-cache policy bitcoin-knots || rpm -q bitcoin-knots || bitcoin-knots --version
2. UPGRADE to 0.16.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade bitcoin-knots
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade bitcoin-knots
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.16.0 (Debian / Ubuntu)
apt-cache madison bitcoin-knots
sudo apt install bitcoin-knots=<VERSION_BEFORE_0.16.0>
sudo apt-mark hold bitcoin-knots
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list bitcoin-knots
sudo dnf downgrade bitcoin-knots-<VERSION_BEFORE_0.16.0>
sudo dnf versionlock add bitcoin-knots
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
btcd project btcd DOWNGRADE
Affected: 0.3.0 alpha · 0.3.1 alpha · 0.3.2 alpha · 0.3.3 alpha · 0.4.0 alpha · 0.5.0 alpha · 0.6.0 alpha · 0.7.0 alpha
Fixed in: no fixed release known
Safe to downgrade to: a release before 0.3.0
1. Check installed version
apt-cache policy btcd || rpm -q btcd || btcd --version
2. No fixed release: DOWNGRADE to a release before 0.3.0 (Debian / Ubuntu)
apt-cache madison btcd
sudo apt install btcd=<VERSION_BEFORE_0.3.0>
sudo apt-mark hold btcd
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list btcd
sudo dnf downgrade btcd-<VERSION_BEFORE_0.3.0>
sudo dnf versionlock add btcd
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
decred dcrd UPGRADE
Affected: < 1.5.2
Fixed in: 1.5.2
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy dcrd || rpm -q dcrd || dcrd --version
2. UPGRADE to 1.5.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade dcrd
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade dcrd
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
litecoin litecoin UPGRADE
Affected: >= 0.16.0 and < 0.16.2
Fixed in: 0.16.2
Safe to downgrade to: a release before 0.16.0
1. Check installed version
apt-cache policy litecoin || rpm -q litecoin || litecoin --version
2. UPGRADE to 0.16.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade litecoin
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade litecoin
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.16.0 (Debian / Ubuntu)
apt-cache madison litecoin
sudo apt install litecoin=<VERSION_BEFORE_0.16.0>
sudo apt-mark hold litecoin
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list litecoin
sudo dnf downgrade litecoin-<VERSION_BEFORE_0.16.0>
sudo dnf versionlock add litecoin
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2018-17145?
bcoin: upgrade to 1.0.2; bitcoin core: upgrade to 0.16.2; bitcoin knots: upgrade to 0.16.2. Exact commands for each OS are on this page.
Is CVE-2018-17145 being exploited?
CVE-2018-17145 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2018-17145 affect?
CVE-2018-17145 affects bcoin, bitcoin core, bitcoin knots. Severity is high (CVSS 7.5). Bitcoin Core 0.16.x before 0.16.2 and Bitcoin Knots 0.16.x before 0.16.2 allow remote denial of service via a flood of multiple transaction inv messages with random hashes, aka INVDoS. NOTE: this can also affect other cryptocurrencies, e.g.
How urgent is CVE-2018-17145?
Priority 59/100. High severity; EPSS top 8%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action
Related CVEs
- CVE-2023-50475 CRITICAL 9.1 DOWNGRADE An issue was discovered in bcoin-org bcoin version 2.2.0, allows remote attackers to obtain sensitive informat