dbcve.org
Bitcoin CoreApplication · Bitcoin

CVE-2015-3641

HIGH · 7.5 CVSS v3.1 Published 2020-03-12
Fix available
A fix is available. Upgrade to 0.10.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
bitcoind and Bitcoin-Qt prior to 0.10.2 allow attackers to cause a denial of service (disabled functionality such as a client application crash) via an "Easy" attack.

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 confidence

Bitcoin Core (bitcoind and Bitcoin-Qt) versions prior to 0.10.2 contain a denial-of-service vulnerability exploitable via an 'Easy' attack vector, allowing remote attackers to crash or disable client functionality.

MitigationUpgrade Bitcoin Core installations to version 0.10.2 or later to remediate this vulnerability.

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
Bitcoin CoreApplication
Affected:< 0.10.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Bitcoin Core version via bitcoind
    Run `bitcoind --version` or `bitcoind -version` in the terminal
    Affected if The version displayed is less than 0.10.2 (e.g., 0.10.1, 0.10.0, etc.)
  2. Check Bitcoin Core version via bitcoin-cli
    Run `bitcoin-cli getinfo` and look for the 'version' field in the output
    Affected if The reported version number is below 100200 (the internal version number for 0.10.2)
  3. Check Bitcoin-Qt GUI version
    Open Bitcoin-Qt and navigate to Help > About Bitcoin-Qt, or check the application window title
    Affected if The version shown is prior to 0.10.2
  4. Verify the Bitcoin Core binary
    Locate the installed binary (commonly in /usr/bin/bitcoind or ~/.bitcoin/ on Linux, or C:\Program Files\Bitcoin\bitcoind.exe on Windows) and run `--version` on it
    Affected if The binary version is older than 0.10.2

If any installed Bitcoin Core component (bitcoind, bitcoin-cli, or Bitcoin-Qt) reports a version lower than 0.10.2, the environment is vulnerable to this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 0.10.2 or later
Fixed in 0.10.2
Interim mitigation

Upgrade Bitcoin Core installations to version 0.10.2 or later to remediate this vulnerability.

Fix this in Bitcoin Core Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-3641 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-3641 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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