VDB-9923 · OSVDB 96174 · GCVE-100-9923

Bitcoin prior 3.15 on Android Random Number Generator improper authentication

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

Summaryinfo

A vulnerability marked as problematic has been reported in Bitcoin on Android. Affected by this issue is some unknown functionality of the component Random Number Generator. The manipulation leads to improper authentication. In addition, an exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Bitcoin on Android (Android App Software) and classified as critical. This issue affects an unknown code of the component Random Number Generator. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability.

The weakness was presented 08/11/2013 as Android Security Vulnerability - 11 August 2013 as not defined alert (Website). It is possible to read the advisory at bitcoin.org. The public release was coordinated in cooperation with the project team. The exploitation is known to be difficult. The attack may be initiated remotely. A simple authentication is needed for exploitation. Technical details are unknown but a private exploit is available. The advisory points out:

Because the problem lies with Android itself, this problem will affect you if you have a wallet generated by any Android app.

Upgrading to version 3.15 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at code.google.com. The best possible mitigation is suggested to be upgrading to the latest version. The alert contains the following remark:

In order to re-secure existing wallets, key rotation is necessary. This involves generating a new address with a repaired random number generator and then sending all the money in your wallet back to yourself. If you use an Android wallet then we strongly recommend you to upgrade to the latest version available in the Play Store as soon as one becomes available. Once your wallet is rotated, you will need to contact anyone who has stored addresses generated by your phone and give them a new one. If you can't update your Android app, alternatively, you can send your bitcoins to a Bitcoin wallet on your computer until your Android app can be updated. You should make sure not to send back your bitcoins to your old insecure addresses.

The vulnerability is also documented in the vulnerability database at OSVDB (96174†). bbc.co.uk is providing further details. See VDB-117166 for similar entry. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Bitcoin Wallet
  • BitcoinSpinner
  • Mycelium Bitcoin Wallet
  • Blockchain

Productinfo

Type

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 6.7

VulDB Base Score: 7.5
VulDB Temp Score: 6.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Improper authentication
CWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Private
Status: Unproven
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Bitcoin 3.15
Patch: code.google.com

Timelineinfo

08/11/2013 🔍
08/14/2013 +3 days 🔍
03/21/2019 +2045 days 🔍

Sourcesinfo

Advisory: Android Security Vulnerability - 11 August 2013
Status: Not defined
Coordinated: 🔍

GCVE (VulDB): GCVE-100-9923
OSVDB: 96174

scip Labs: https://www.scip.ch/en/?labs.20130704
Misc.: 🔍
See also: 🔍

Entryinfo

Created: 08/14/2013 16:37
Updated: 03/21/2019 10:37
Changes: 08/14/2013 16:37 (50), 03/21/2019 10:37 (2)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

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!