LiveActive security incident?Get immediate response
CVE Record

CVE-2013-3220: bitcoind and Bitcoin-Qt before 0.4.9rc2, 0.5.x before 0.5.8rc2, 0.6.x before 0.6.5rc2, and 0.7.x before 0.7...

bitcoind and Bitcoin-Qt before 0.4.9rc2, 0.5.x before 0.5.8rc2, 0.6.x before 0.6.5rc2, and 0.7.x before 0.7.3rc2, and wxBitcoin, do not properly consider whether a block's size could require an excessive number of database locks, which allows remote attackers to cause a denial of service (split) and enable certain double-spending capabilities via a large block that triggers incorrect Berkeley DB locking.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a historical Bitcoin client flaw where specially large blocks could trigger database-lock handling problems, causing a network split and enabling some double-spending scenarios. The main business concern is any legacy Bitcoin node software still running vulnerable versions.

Executive priority

Treat this as high priority only if the organization operates legacy Bitcoin nodes or custody/payment infrastructure. For ordinary environments without old Bitcoin clients, urgency is low after confirming absence of affected software.

Technical view

Affected bitcoind, Bitcoin-Qt, and wxBitcoin versions did not properly account for block size effects on Berkeley DB lock usage. A remote attacker could use a large block to trigger incorrect locking behavior, causing denial of service through chain split conditions and limited double-spend capability.

Likely exposure

Exposure is mainly legacy Bitcoin infrastructure running the specific pre-0.4.9rc2, pre-0.5.8rc2, pre-0.6.5rc2, or pre-0.7.3rc2 clients, plus wxBitcoin. Modern deployments are unlikely to be affected unless old binaries remain in use.

Exploitation context

The source bundle does not show CISA KEV listing or current active exploitation. The CVE record describes remote attack potential and impact, but does not provide current exploit activity, exploit availability, or proof-of-concept status.

Researcher notes

Evidence is limited to the CVE description and Bitcoin wiki references. No CVSS, CWE, CPE, or KEV data is provided. The affected list in the bundle is generic, so validation should rely on exact software names and versions from the description.

Mitigation direction

  • Inventory Bitcoin node software and record exact product and version.
  • Upgrade vulnerable bitcoind or Bitcoin-Qt versions beyond the listed fixed release candidates.
  • Remove or isolate wxBitcoin deployments until vendor guidance confirms safety.
  • Check Bitcoin project guidance for historically recommended client versions and migration steps.
  • Prioritize systems involved in transaction validation, custody, or payment processing.

Validation and detection

  • Confirm no production node runs the vulnerable version ranges listed in the CVE.
  • Check package inventories, container images, and old host snapshots for legacy Bitcoin binaries.
  • Review node logs around historical or test environments for split or database-lock errors.
  • Verify upgrade evidence with binary version output or package manager records.
  • Document whether wxBitcoin exists anywhere in the environment.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2013-3220 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.