dbcve.org
Bitcoin CoreApplication · Bitcoin

CVE-2013-4627

MEDIUM · 5.0 CVSS v2.0 Published 2013-08-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Unspecified vulnerability in bitcoind and Bitcoin-Qt 0.8.x allows remote attackers to cause a denial of service (memory consumption) via a large amount of tx message data.

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

Remote denial of service vulnerability in bitcoind and Bitcoin-Qt 0.8.x allows attackers to cause memory exhaustion by sending large amounts of transaction (tx) message data, potentially crashing the node.

MitigationUpgrade to a patched Bitcoin software version newer than 0.8.x; consider implementing network-level rate limiting or connection limits as a compensating control until upgrade is possible.

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.8.0= 0.8.1

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 installed Bitcoin Core version
    Run `bitcoind --version` or `bitcoin-cli getversion` to identify the running software version
    Affected if Version displayed is exactly 0.8.0 or 0.8.1
  2. Verify P2P network service is enabled
    Check if the node is configured to accept incoming connections by examining bitcoin.conf for `listen=1` or using `bitcoin-cli getnetworkinfo` to check `listening` status
    Affected if P2P listening is enabled and the node accepts inbound connections on port 8333 (mainnet) or 8334 (testnet)
  3. Confirm memory usage and process stability
    Monitor current memory consumption of the bitcoind process using system tools like `ps aux | grep bitcoind` or `top` and note if the process is running
    Affected if The node is actively running and network-accessible, making it vulnerable to the memory exhaustion attack vector

The environment is affected if Bitcoin Core version 0.8.0 or 0.8.1 is running with P2P network listening enabled, exposing it to remote attackers who can send large transaction messages to cause memory exhaustion.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched Bitcoin software version newer than 0.8.x; consider implementing network-level rate limiting or connection limits as a compensating control until upgrade is possible.

Fix this in Bitcoin Core Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-4627 — 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-2013-4627 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