VulnSocial

CVE-2013-3220General(bitcoin / bitcoin-qt)

LOWCVSS 6.4 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch bitcoin bitcoin-qt systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

bitcoin CVEsBack to dashboard
1.0/ 10 priority

Sources & remediation

Vendor / third-party advisories
Weakness type (CWE)
CWE-399

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • bitcoin-qt
  • bitcoin_core
  • bitcoind
  • qitcoin-qt

Threat summary

  • Patch or workaround signal is available
  • 4 mentions across 4 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 2 signals
  • General: 3 classified signals
  • Peaked 3d ago at 1 mentions (2026-03-15); latest day: 1
  • 4 total mentions across 4 days

Affected systems

Vendors
bitcoin
Products
bitcoin-qtbitcoin_corebitcoindqitcoin-qt

46 versions affected across 4 products

Deep dive

Activity timeline4 mentions / 4d
00111Mentions · 2026-03-15: 1Mentions · 2026-04-29: 1Mentions · 2026-08-06: 1Mentions · 2026-08-13: 1Patch / Workaround · 2026-03-15: 1Patch / Workaround · 2026-08-06: 103-1504-2908-0608-13
Signal classification2 categories
General
375.0%
Patch
125.0%
Classification over time
DateTotalLabels
2026-03-151
General1
2026-04-291
General1
2026-08-061
Patch1
2026-08-131
General1
Full discourse4 posts
  • Marco ₿attistoni@Battistoshi93
    General

    The ₿itcoin network has again an uptime > 99.99%. Last 2 downtime events: -August 15, 2010 CVE-2010-513: off 8h & 27m -March 12, 2013 CVE-2013-3220: off 6h & 20m Since 2010's bug fixed by Satoshi himself and 2013 network split, the ₿itcoin network never missed a beat! https://t.co/gVDi1a2eSI

    Post summary

    The tweet lists two historical Bitcoin network downtimes tied to CVE-2010-513 and CVE-2013-3220, noting that the vulnerability was fixed and the network now enjoys sustained uptime.

    10082212
    4.8K followersView on X
  • Bitcoin Butlers@bitcoinbutlers
    General

    @JWWeatherman_ @SeedSigner CVE-2010-5139, CVE-2018-17144, CVE-2013-3220, CVE-2012-2459, CVE-2011-4447 and you only said no to part of the issue raised - single point of failure, OP also references merely one potential part of a quorum.

    Post summary

    The tweet lists several CVE identifiers but offers no technical details, exploit information, or patch guidance.

    00160223
    764 followersView on X
  • Cryptonite Uae@CryptoniteUae
    Patch

    Someone double-spent 211.9 BTC against a payment processor during the window — then posted the full sequence publicly. An experiment, not an attack. The lock rule was finally retired 16 Aug 2013, at block 252,451. CVE-2013-3220.

    Post summary

    The post notes that CVE-2013-3220’s lock rule was retired, but provides no exploit details, PoC, or evidence of active usage.

    1000058
    2.9K followersView on X
  • anon_sats@anon_sats
    General

    @S4toshis_Secret @sebp888 CVE-2013-3220

    Post summary

    The tweet mentions CVE-2013-3220 but provides no additional information or context.

    0000042
    255 followersView on X
CPE platform detail63 entries

63 of 63 entries

PartVendorProductVersionTarget SWTarget HW
Appbitcoinbitcoin-qt---
Appbitcoinbitcoin-qt0.4--
Appbitcoinbitcoin-qt0.4.8--
Appbitcoinbitcoin-qt0.5.0--
Appbitcoinbitcoin-qt0.5.0.4--
Appbitcoinbitcoin-qt0.5.1--
Appbitcoinbitcoin-qt0.5.3.0--
Appbitcoinbitcoin-qt0.5.7--
Appbitcoinbitcoin-qt0.5.8--
Appbitcoinbitcoin-qt0.6.0.10--
Appbitcoinbitcoin-qt0.6.3--
Appbitcoinbitcoin-qt0.7.0--
Appbitcoinbitcoin-qt0.7.1--
Appbitcoinbitcoin-qt0.7.2--
Appbitcoinbitcoin-qt0.7.3--
Appbitcoinbitcoin_core---
Appbitcoinbitcoin_core0.3.10--
Appbitcoinbitcoin_core0.3.11--
Appbitcoinbitcoin_core0.3.12--
Appbitcoinbitcoin_core0.3.4--
Appbitcoinbitcoin_core0.3.5--
Appbitcoinbitcoin_core0.3.8--
Appbitcoinbitcoin_core0.4.0--
Appbitcoinbitcoin_core0.4.1--
Appbitcoinbitcoin_core0.4.1--
Appbitcoinbitcoin_core0.4.2--
Appbitcoinbitcoin_core0.4.3--
Appbitcoinbitcoin_core0.4.4--
Appbitcoinbitcoin_core0.4.4--
Appbitcoinbitcoin_core0.4.5--
Appbitcoinbitcoin_core0.4.6--
Appbitcoinbitcoin_core0.4.7--
Appbitcoinbitcoin_core0.5.0--
Appbitcoinbitcoin_core0.5.3--
Appbitcoinbitcoin_core0.5.3.1--
Appbitcoinbitcoin_core0.5.4--
Appbitcoinbitcoin_core0.5.5--
Appbitcoinbitcoin_core0.5.6--
Appbitcoinbitcoin_core0.6.0.1--
Appbitcoinbitcoin_core0.6.0.2--
Appbitcoinbitcoin_core0.6.0.3--
Appbitcoinbitcoin_core0.6.0.4--
Appbitcoinbitcoin_core0.6.0.5--
Appbitcoinbitcoin_core0.6.0.6--
Appbitcoinbitcoin_core0.6.0.7--
Appbitcoinbitcoin_core0.6.0.8--
Appbitcoinbitcoin_core0.6.1--
Appbitcoinbitcoin_core0.6.2--
Appbitcoinbitcoind---
Appbitcoinbitcoind0.4.4--
Appbitcoinbitcoind0.5.7--
Appbitcoinbitcoind0.5.8--
Appbitcoinbitcoind0.6.0.0--
Appbitcoinbitcoind0.6.0.10--
Appbitcoinbitcoind0.6.3--
Appbitcoinbitcoind0.6.4--
Appbitcoinbitcoind0.6.5--
Appbitcoinbitcoind0.7.0--
Appbitcoinbitcoind0.7.1--
Appbitcoinbitcoind0.7.2--
Appbitcoinbitcoind0.7.3--
Appbitcoinqitcoin-qt0.6.4--
Appbitcoinqitcoin-qt0.6.5--

Explore more

Back to dashboardbitcoin CVEsbitcoin-qt vulnerabilities