CVE-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 flood of multiple transaction…
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.7% (FIRST EPSS); higher than 92% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: bcoin (npm) 1.0.2.
Low priority for now. Upgrade to bcoin (npm) 1.0.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 10, 2020
- Updated
- Jun 16, 2026
- EPSS
- 4.7% · 92th percentile
- CWE
- CWE-400
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| bitcoin | bitcoin core | cpe:2.3:a:bitcoin:bitcoin_core |
| bcoin | bcoin | cpe:2.3:a:bcoin:bcoin |
| bitcoinknots | bitcoin knots | cpe:2.3:a:bitcoinknots:bitcoin_knots |
| btcd project | btcd | cpe:2.3:a:btcd_project:btcd |
| decred | dcrd | cpe:2.3:a:decred:dcrd |
| litecoin | litecoin | cpe:2.3:a:litecoin:litecoin |
| namecoin | namecoin core | cpe:2.3:a:namecoin:namecoin_core |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- bcoin bcoinbefore 1.0.2
- bitcoin bitcoin core0.16.0 and later · before 0.16.2
- bitcoinknots bitcoin knots0.16.0 and later · before 0.16.2
- btcd project btcd0.10.0
- btcd project btcd0.11.0
- btcd project btcd0.11.1
- btcd project btcd0.12.0
- btcd project btcd0.13.0
+12 more rows
- btcd project btcd0.20.0
- btcd project btcd0.20.1
- btcd project btcd0.3.0
- btcd project btcd0.3.1
- btcd project btcd0.3.2
- btcd project btcd0.3.3
- btcd project btcd0.4.0
- btcd project btcd0.5.0
- btcd project btcd0.6.0
- btcd project btcd0.7.0
- btcd project btcd0.8.0
- btcd project btcd0.9.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | bcoin | before 1.0.2 | 1.0.2 |
Same product
bitcoin: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-17144Bitcoin 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…32Monitor
- CVE-2020-14198Bitcoin Core 0.20.0 allows remote denial of service.31Monitor
- CVE-2017-12842Bitcoin 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…31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2017-18350Mar 12, 2020 · bitcoind and Bitcoin-Qt prior to 0.15.1 have a stack-based buffer overflow if an attacker-controlled SOCKS proxy server is used.23Monitor
- ← EarlierCVE-2018-20586Mar 12, 2020 · bitcoind and Bitcoin-Qt prior to 0.17.1 allow injection of arbitrary data into the debug log via an RPC call.21Monitor
- Later →CVE-2021-3195Jan 26, 2021 · bitcoind in Bitcoin Core through 0.21.0 can create a new file in an arbitrary directory (e.g., outside the ~/.bitcoin directory) via a…30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:bcoin | 1.0.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.