Bitcoin bitcoind up to 0.4.4 config

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.1$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Bitcoin bitcoind up to 0.4.4. Affected by this issue is some unknown functionality. The manipulation leads to config. This vulnerability is traded as CVE-2012-1909. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Bitcoin bitcoind up to 0.4.4. It has been rated as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a config vulnerability. Using CWE to declare the problem leads to CWE-16. Impacted is availability. The summary by CVE is:

The Bitcoin protocol, as used in bitcoind before 0.4.4, wxBitcoin, Bitcoin-Qt, and other programs, does not properly handle multiple transactions with the same identifier, which allows remote attackers to cause a denial of service (unspendable transaction) by leveraging the ability to create a duplicate coinbase transaction.

The weakness was shared 08/06/2012 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2012-1909 since 03/26/2012. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592.004 for this issue.

Upgrading to version 0.3.12 eliminates this vulnerability.

The entries VDB-61468, VDB-61467, VDB-61466 and VDB-61465 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1

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

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Config
CWE: CWE-16
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: bitcoind 0.3.12
Patch: github.com

Timelineinfo

03/26/2012 🔍
08/06/2012 +133 days 🔍
08/06/2012 +0 days 🔍
03/23/2015 +959 days 🔍
12/07/2021 +2451 days 🔍

Sourcesinfo

Advisory: a206b0ea12eb4606b93323268fc81a4f1f952531
Status: Not defined
Confirmation: 🔍

CVE: CVE-2012-1909 (🔍)
GCVE (CVE): GCVE-0-2012-1909
GCVE (VulDB): GCVE-100-61469
See also: 🔍

Entryinfo

Created: 03/23/2015 16:50
Updated: 12/07/2021 09:24
Changes: 03/23/2015 16:50 (47), 02/19/2019 11:16 (2), 12/07/2021 09:24 (4)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!