Bitcoin Inventory Out-of-Memory Denial-of-Service Attack (CVE-2018-17145)GHSA-hx3r-jv9q-85jw
HIGHGHSA-hx3r-jv9q-85jw is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in bcoin. 1 public exploit reference exists, so weaponization risk is real. A fix is available for bcoin — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-hx3r-jv9q-85jw by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
bcoinnpmDescription
There was an easily exploitable uncontrolled memory resource consumption denial-of-service vulnerability that existed in the peer-to-peer network code of three implementations of Bitcoin and several alternative chains.
For more details please see: https://invdos.net/
For the paper: https://invdos.net/paper/CVE-2018-17145.pdf
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | bcoin | all versions | 1.0.2npm install bcoin@1.0.2 |
Affected Products
bcoinbcoinbitcoin corebitcoinbitcoin knotsbitcoinknotsbtcdbtcd_projectdcrddecredlitecoinlitecoinResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bcoin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bcoin to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hx3r-jv9q-85jw is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-hx3r-jv9q-85jw in your dependencies?
Find it across npm, including transitive dependencies.