CVE-2018-1000893
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 deserializing transactions.
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 in its transaction deserialization logic where malformed or malicious transaction data can trigger uncontrolled resource consumption, potentially leading to denial of service through memory exhaustion or CPU exhaustion.
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 installed Bitcoin SV versionRun 'bitcoind -version' or 'bitcoin-sv -version' from the command line, or check the package/version information where the software was installedAffected if The reported version is below 0.1.1 (e.g., 0.1.0, 0.0.x, or any nightly build earlier than the 0.1.1 release)
-
Verify node is operationalCheck if the bitcoind or bitcoin-sv process is running (e.g., 'ps aux | grep bitcoind' or 'systemctl status bitcoind') and if the RPC interface responds to 'getblockchaininfo'Affected if The node is running and actively processing blocks or transactions, as the vulnerability triggers during transaction deserialization
-
Confirm transaction processing is enabledCheck the configuration file (bitcoin.conf) for 'disablewallet=1' or 'blocksonly=1' settings - if neither is set, the wallet and transaction relay are enabledAffected if Transaction processing is enabled (default behavior), which allows the node to receive and deserialize transactions from the network
You are affected if your Bitcoin SV node version is below 0.1.1 and the node is running with transaction processing enabled, as malformed transaction data can trigger uncontrolled resource consumption during deserialization.
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
Upgrade Bitcoin SV node software to version 0.1.1 or later which addresses the uncontrolled resource consumption in transaction deserialization. For production systems, also implement network-level rate limiting and transaction size limits as defense-in-depth.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000893 — 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-1000893 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