CVE-2018-1000891
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBitcoin SV before 0.1.1 allows uncontrolled resource consumption when receiving messages with invalid checksums.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceBitcoin SV before version 0.1.1 contains a vulnerability where processing messages with invalid checksums leads to uncontrolled resource consumption. This creates a denial-of-service condition where an attacker sending specially crafted messages with invalid checksums can exhaust node resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.1.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Bitcoin SV installationLocate the bitcoin-sv executable or service on the system. Common paths include /usr/bin/bitcoin-sv, /usr/local/bin/bitcoin-sv, or check running services with 'ps aux | grep bitcoin'Affected if Bitcoin SV software is installed and running
-
Determine installed versionRun 'bitcoin-sv --version' or 'bitcoind -version' to obtain the exact version numberAffected if Version is below 0.1.1 (e.g., 0.1.0 or earlier)
-
Verify P2P network is enabledCheck configuration file (bitcoin.conf) for 'listen=1' or 'listenonion=1' settings, or check if port 8333 (mainnet) or 8334 (testnet) is open with 'netstat -tlnp | grep 833'Affected if The node is configured to accept incoming P2P connections (listen mode enabled)
-
Confirm node is network-reachableCheck if the P2P port is exposed externally via firewall rules or router port forwarding. Use 'iptables -L' or check router configurationAffected if The node is accessible from external network sources
You are affected if Bitcoin SV version is below 0.1.1 AND the node is running with P2P network listening enabled, as the vulnerability triggers when processing incoming messages with invalid checksums.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data0.1.1
Update Bitcoin SV to version 0.1.1 or later to patch the vulnerability. Consider network-level rate limiting or firewall rules as additional defense-in-depth measures until the patch can be applied.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000891 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1000891 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data