Strix
26.1K

CVE-2013-3220

UnknownEPSS 2.38%

Last modified

CVE-2013-3220 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.38% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
2.38%

81.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
BitcoinBitcoin-Qt<= 0.4.9Rc1
BitcoinBitcoin-Qt0.4Rc4
BitcoinBitcoin-Qt0.4.8Rc4
BitcoinBitcoin-Qt0.5.0Rc1
BitcoinBitcoin-Qt0.5.0.4—
BitcoinBitcoin-Qt0.5.1Rc1
BitcoinBitcoin-Qt0.5.3.0—
BitcoinBitcoin-Qt0.5.7—
BitcoinBitcoin-Qt0.5.8Rc1
BitcoinBitcoin-Qt0.6.0.10Rc4
BitcoinBitcoin-Qt0.6.3—
BitcoinBitcoin-Qt0.7.0Rc1
BitcoinBitcoin-Qt0.7.1—
BitcoinBitcoin-Qt0.7.2—
BitcoinBitcoin-Qt0.7.3Rc1
BitcoinBitcoin CoreAll versions—
BitcoinBitcoin Core0.3.4—
BitcoinBitcoin Core0.3.5—
BitcoinBitcoin Core0.3.8—
BitcoinBitcoin Core0.3.10—
BitcoinBitcoin Core0.3.11—
BitcoinBitcoin Core0.3.12—
BitcoinBitcoin Core0.4.0—
BitcoinBitcoin Core0.4.1—
BitcoinBitcoin Core0.4.2—
BitcoinBitcoin Core0.4.3—
BitcoinBitcoin Core0.4.4—
BitcoinBitcoin Core0.4.5—
BitcoinBitcoin Core0.4.6—
BitcoinBitcoin Core0.4.7Rc2
BitcoinBitcoin Core0.5.0Rc
BitcoinBitcoin Core0.5.3—
BitcoinBitcoin Core0.5.3.1—
BitcoinBitcoin Core0.5.4—
BitcoinBitcoin Core0.5.5—
BitcoinBitcoin Core0.5.6Rc2
BitcoinBitcoin Core0.6.0.1—
BitcoinBitcoin Core0.6.0.2—
BitcoinBitcoin Core0.6.0.3—
BitcoinBitcoin Core0.6.0.4—
BitcoinBitcoin Core0.6.0.5—
BitcoinBitcoin Core0.6.0.6—
BitcoinBitcoin Core0.6.0.7—
BitcoinBitcoin Core0.6.0.8—
BitcoinBitcoin Core0.6.1—
BitcoinBitcoin Core0.6.2—
BitcoinBitcoind<= 0.4.9Rc1
BitcoinBitcoind0.4.4Rc4
BitcoinBitcoind0.5.7—
BitcoinBitcoind0.5.8Rc1

Showing 50 of 61 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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.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.
How severe is CVE-2013-3220?
Severity scoring for CVE-2013-3220 is pending analysis. The EPSS model estimates a 2.38% probability of exploitation in the next 30 days.
How do I fix CVE-2013-3220?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2013

View all 2013CVEs →

Are you affected by CVE-2013-3220?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST