| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.23 |
Summary
A vulnerability marked as problematic has been reported in Bitcoin. Affected is the function AES Encryption Padding of the file wallet.dat. The manipulation leads to missing encryption.
The attack must be carried out locally. There is no available exploit.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in Bitcoin (the affected version is unknown) and classified as critical. This issue affects the function AES Encryption Padding of the file wallet.dat. The manipulation with an unknown input leads to a missing encryption vulnerability. Using CWE to declare the problem leads to CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. Impacted is confidentiality, and integrity.
The weakness was presented 03/18/2012 by etotheipi as not defined mailinglist post (GitHub Repository). It is possible to read the advisory at github.com. Attacking locally is a requirement. A simple authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at OSVDB (80337†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Website
- Product: https://github.com/bitcoin/bitcoin/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 6.3
VulDB Base Score: 7.1
VulDB Temp Score: 6.3
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: Missing encryptionCWE: CWE-311 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
03/18/2012 🔍03/23/2012 🔍
03/24/2012 🔍
09/05/2019 🔍
Sources
Product: github.comAdvisory: github.com
Researcher: etotheipi
Status: Not defined
GCVE (VulDB): GCVE-100-4883
OSVDB: 80337
Entry
Created: 03/24/2012 15:49Updated: 09/05/2019 13:38
Changes: 03/24/2012 15:49 (42), 09/05/2019 13:38 (1)
Complete: 🔍
Cache ID: 216:18B: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.