Bitcoin Project Bitcoin-Qt up to 0.6.3 Transaction resource management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Bitcoin Project Bitcoin-Qt up to 0.6.3. It has been rated as problematic. The affected element is an unknown function of the component Transaction Handler. Performing a manipulation results in resource management. This vulnerability is identified as CVE-2013-3220. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in Bitcoin Project Bitcoin-Qt up to 0.6.3 (Project Management Software). It has been classified as problematic. This affects an unknown function of the component Transaction Handler. The manipulation with an unknown input leads to a resource management vulnerability. CWE is classifying the issue as CWE-399. This is going to have an impact on integrity. The summary by CVE is:
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.
The weakness was released 03/25/2013 as BIP-0034 as not defined changelog entry (Website). The advisory is shared at en.bitcoin.it. The public release was coordinated with Bitcoin Project. This vulnerability is uniquely identified as CVE-2013-3220 since 04/20/2013. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.6.4rc1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (92255†). Entry connected to this vulnerability is available at VDB-8250. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Resource managementCWE: CWE-399 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Bitcoin-Qt 0.6.4rc1
Timeline
03/25/2013 🔍03/25/2013 🔍
04/17/2013 🔍
04/20/2013 🔍
08/02/2013 🔍
05/05/2018 🔍
Sources
Advisory: BIP-0034Status: Not defined
Confirmation: 🔍
Coordinated: 🔍
CVE: CVE-2013-3220 (🔍)
GCVE (CVE): GCVE-0-2013-3220
GCVE (VulDB): GCVE-100-8421
OSVDB: 92255
See also: 🔍
Entry
Created: 04/17/2013 17:29Updated: 05/05/2018 18:05
Changes: 04/17/2013 17:29 (51), 05/05/2018 18:05 (6)
Complete: 🔍
Committer:
Cache ID: 216:58C:103
No comments yet. Languages: en.
Please log in to comment.