bitcoin bitcoind up to 0.4.0 FetchInputs Stored resource management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in bitcoin bitcoind up to 0.4.0 and classified as problematic. This affects the function CTransaction::FetchInputs. The manipulation leads to resource management (Stored).
This vulnerability is documented as CVE-2013-2293. There is not any exploit available.
The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, has been found in bitcoin bitcoind up to 0.4.0. This issue affects the function CTransaction::FetchInputs. The manipulation with an unknown input leads to a resource management vulnerability (Stored). Using CWE to declare the problem leads to CWE-399. Impacted is availability. The summary by CVE is:
The CTransaction::FetchInputs method in bitcoind and Bitcoin-Qt before 0.8.0rc1 copies transactions from disk to memory without incrementally checking for spent prevouts, which allows remote attackers to cause a denial of service (disk I/O consumption) via a Bitcoin transaction with many inputs corresponding to many different parts of the stored block chain.
The weakness was released 03/12/2013 (Website). It is possible to read the advisory at en.bitcoin.it. The identification of this vulnerability is CVE-2013-2293 since 02/28/2013. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 0.4.1 eliminates this vulnerability.
Entries connected to this vulnerability are available at VDB-61475, VDB-61471, VDB-61468 and VDB-61467. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
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
Name: StoredClass: Resource management / Stored
CWE: 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: 🔍
0-Day Time: 🔍
Upgrade: bitcoind 0.4.1
Timeline
02/28/2013 🔍03/12/2013 🔍
03/12/2013 🔍
03/24/2015 🔍
02/25/2019 🔍
Sources
Advisory: en.bitcoin.itStatus: Not defined
Confirmation: 🔍
CVE: CVE-2013-2293 (🔍)
GCVE (CVE): GCVE-0-2013-2293
GCVE (VulDB): GCVE-100-63731
See also: 🔍
Entry
Created: 03/24/2015 12:22Updated: 02/25/2019 11:17
Changes: 03/24/2015 12:22 (49), 02/25/2019 11:17 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.