Bitcoin Project bitcoind 0.8.1 RPC Authentication Mechanism information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Bitcoin Project bitcoind 0.8.1. This issue affects some unknown processing of the component RPC Authentication Mechanism. This manipulation causes information disclosure. The identification of this vulnerability is CVE-2013-4165. Furthermore, there is an exploit available.
Details
A vulnerability classified as problematic was found in Bitcoin Project bitcoind 0.8.1 (Project Management Software). Affected by this vulnerability is some unknown functionality of the component RPC Authentication Mechanism. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
The HTTPAuthorized function in bitcoinrpc.cpp in bitcoind 0.8.1 provides information about authentication failure upon detecting the first incorrect byte of a password, which makes it easier for remote attackers to determine passwords via a timing side-channel attack.
The weakness was shared 07/20/2013 as not defined git commit (GIT Repository). It is possible to read the advisory at github.com. The vendor cooperated in the coordination of the public release. This vulnerability is known as CVE-2013-4165 since 06/12/2013. 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. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
After immediately, there has been an exploit disclosed. It is possible to download the exploit at github.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at OSVDB (95618†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
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.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
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
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
06/12/2013 🔍07/20/2013 🔍
07/20/2013 🔍
07/26/2013 🔍
08/02/2013 🔍
05/08/2018 🔍
Sources
Advisory: github.comStatus: Not defined
Coordinated: 🔍
CVE: CVE-2013-4165 (🔍)
GCVE (CVE): GCVE-0-2013-4165
GCVE (VulDB): GCVE-100-9739
OSVDB: 95618
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/26/2013 17:48Updated: 05/08/2018 08:54
Changes: 07/26/2013 17:48 (50), 05/08/2018 08:54 (6)
Complete: 🔍
Committer:
Cache ID: 216:2E2:103
No comments yet. Languages: en.
Please log in to comment.