Google Android up to 4.3.1 SHA1PRNG_SecureRandomImpl.java engineNextBytes cryptographic issue

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.
5.3$5k-$25k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Google Android up to 4.3.1. This issue affects the function engineNextBytes in the library classlib/modules/security/src/main/java/common/org/apache/harmony/security/provider/crypto/SHA1PRNG_SecureRandomImpl.java. This manipulation causes cryptographic issue. This vulnerability is registered as CVE-2013-7372. No exploit is available.

Detailsinfo

A vulnerability classified as problematic was found in Google Android up to 4.3.1 (Smartphone Operating System). Affected by this vulnerability is the function engineNextBytes in the library classlib/modules/security/src/main/java/common/org/apache/harmony/security/provider/crypto/SHA1PRNG_SecureRandomImpl.java. The manipulation with an unknown input leads to a cryptographic issue vulnerability. The CWE definition for the vulnerability is CWE-310. As an impact it is known to affect integrity. The summary by CVE is:

The engineNextBytes function in classlib/modules/security/src/main/java/common/org/apache/harmony/security/provider/crypto/SHA1PRNG_SecureRandomImpl.java in the SecureRandom implementation in Apache Harmony through 6.0M3, as used in the Java Cryptography Architecture (JCA) in Android before 4.4 and other products, when no seed is provided by the user, uses an incorrect offset value, which makes it easier for attackers to defeat cryptographic protection mechanisms by leveraging the resulting PRNG predictability, as exploited in the wild against Bitcoin wallet applications in August 2013.

The weakness was published 04/29/2014 (Website). It is possible to read the advisory at android.googlesource.com. This vulnerability is known as CVE-2013-7372 since 04/29/2014. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 07/13/2024). It is expected to see the exploit prices for this product increasing in the near future.The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.

It is declared as attacked.

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 databases at X-Force (95236), Zero-Day.cz (342), SecurityFocus (BID 68229†) and Vulnerability Center (SBV-47677†). Similar entry is available at VDB-69536. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Cryptographic issue
CWE: CWE-310
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Attacked

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Zero-Day.cz: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

08/11/2013 🔍
04/29/2014 +261 days 🔍
04/29/2014 +0 days 🔍
04/29/2014 +0 days 🔍
04/30/2014 +1 days 🔍
12/17/2014 +231 days 🔍
03/25/2015 +98 days 🔍
07/13/2024 +3398 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: android.googlesource.com
Status: Not defined
Confirmation: 🔍

CVE: CVE-2013-7372 (🔍)
GCVE (CVE): GCVE-0-2013-7372
GCVE (VulDB): GCVE-100-69535
X-Force: 95236
SecurityFocus: 68229 - Apache Harmony PRNG Entropy Weakness
Vulnerability Center: 47677 - Apache Harmony 6.0M3 on Google Android <4.4 Allows Cryptographic Weaknesses, Medium

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

Entryinfo

Created: 03/25/2015 16:45
Updated: 07/13/2024 23:12
Changes: 03/25/2015 16:45 (57), 06/15/2017 11:41 (4), 07/13/2024 23:12 (21)
Complete: 🔍
Cache ID: 216:2FE:103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!