| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Bitcoin. Affected is an unknown function of the component Payment Handler. This manipulation causes race condition. Moreover, an exploit is present. It is advised to substitute the affected component with an alternative.
Details
A vulnerability was found in Bitcoin (the affected version is unknown). It has been declared as critical. Affected by this vulnerability is an unknown code of the component Payment Handler. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, and integrity.
The weakness was disclosed 09/24/2012 by Ghassan O.Karame, Elli Androulaki and Srdjan Capkun with NEC Laboratories Europe/ETH Zürich as bitcoin-double-spend as not defined blog post (Website). The advisory is shared at codinginmysleep.com. The public release happened without involvement of the project team. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. A flaw in the time reporting of a transaction leads to a possibly succsessful double-spending attack.
After immediately, there has been an exploit disclosed. It is possible to download the exploit at eprint.iacr.org. It is declared as proof-of-concept.
The problem might be mitigated by replacing the product with as an alternative. Since this is a design flaw of Bitcoin addressing the fast payments without confirmation. The use of this fast payments should be avoided until Bitcoin has addressed this issue.
The vulnerability is also documented in the vulnerability database at OSVDB (85871†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.1VulDB Meta Temp Score: 8.6
VulDB Base Score: 9.1
VulDB Temp Score: 8.6
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: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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: AlternativeStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
09/24/2012 🔍09/24/2012 🔍
09/30/2012 🔍
10/04/2012 🔍
05/01/2018 🔍
Sources
Advisory: bitcoin-double-spendResearcher: Ghassan O.Karame, Elli Androulaki, Srdjan Capkun
Organization: NEC Laboratories Europe/ETH Zürich
Status: Not defined
GCVE (VulDB): GCVE-100-6577
OSVDB: 85871
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/04/2012 11:02Updated: 05/01/2018 12:24
Changes: 10/04/2012 11:02 (49), 05/01/2018 12:24 (1)
Complete: 🔍
Committer: olku
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.