Bitcoin Project bitcoind/Bitcoin-Qt/wxBitcoin up to 0.7.3rc1 Large Block access control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability was found in Bitcoin Project bitcoind, Bitcoin-Qt and wxBitcoin up to 0.7.3rc1 and classified as critical. Affected by this vulnerability is an unknown functionality of the component Large Block Handler. The manipulation results in access control. This vulnerability is known as CVE-2013-3219. Furthermore, an exploit is available. This vulnerability has historical importance owing to its background and reception. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Bitcoin Project bitcoind, Bitcoin-Qt and wxBitcoin up to 0.7.3rc1 (Project Management Software). It has been classified as critical. Affected is an unknown code of the component Large Block Handler. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on integrity. CVE summarizes:

bitcoind and Bitcoin-Qt 0.8.x before 0.8.1 do not enforce a certain block protocol rule, which allows remote attackers to bypass intended access restrictions and conduct double-spending attacks via a large block that triggers incorrect Berkeley DB locking in older product versions.

The weakness was published 03/11/2013 as Unassigned-20120311 as not defined changelog entry (Website). The advisory is available at en.bitcoin.it. The changelog entry contains:

Bitcoin contains a flaw related to a block containing a previously unseen number of total transaction inputs being mined and broadcasted. Bitcoin nodes of version 0.8 could handle this quantity, but nodes before 0.8 could not, which effectively forked the product chain. This allowed an attacker to potentially spend the same currency twice, once on each of the forks.
This vulnerability is traded as CVE-2013-3219 since 04/20/2013. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are unknown but a public exploit is available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 05/08/2021). This vulnerability is assigned to T1068 by the MITRE ATT&CK project. This vulnerability has a historic impact due to its background and reception.

It is declared as proof-of-concept.

Upgrading to version 0.8.1 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 (92253†). Further details are available at en.bitcoin.it. Similar entry is available at VDB-8421. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.9
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.9
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: bitcoind/Bitcoin-Qt/wxBitcoin 0.8.1

Timelineinfo

03/11/2013 🔍
03/11/2013 +0 days 🔍
04/16/2013 +36 days 🔍
04/20/2013 +4 days 🔍
08/02/2013 +104 days 🔍
05/08/2021 +2836 days 🔍

Sourcesinfo

Advisory: Unassigned-20120311
Status: Not defined
Confirmation: 🔍

CVE: CVE-2013-3219 (🔍)
GCVE (CVE): GCVE-0-2013-3219
GCVE (VulDB): GCVE-100-8250
OSVDB: 92253 - bitcoind / Bitcoin-Qt Large Block Split Double Spending Weakness

scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
See also: 🔍

Entryinfo

Created: 04/16/2013 18:01
Updated: 05/08/2021 08:54
Changes: 04/16/2013 18:01 (51), 12/16/2015 10:22 (5), 05/08/2021 08:54 (8)
Complete: 🔍
Cache ID: 216:AD3:103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!