First published: Tue Apr 29 2014(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Harmony | <=6.0 | |
Google Android | <=4.3.1 | |
Google Android | =4.0 | |
Google Android | =4.0.1 | |
Google Android | =4.0.2 | |
Google Android | =4.0.3 | |
Google Android | =4.0.4 | |
Google Android | =4.1 | |
Google Android | =4.1.2 | |
Google Android | =4.2 | |
Google Android | =4.2.1 | |
Google Android | =4.2.2 | |
Google Android | =4.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-7372 is considered a high severity vulnerability due to potential predictability in generated cryptographic random numbers.
To fix CVE-2013-7372, upgrade to a version of Apache Harmony later than 6.0M3 or an Android version later than 4.3.
CVE-2013-7372 affects Apache Harmony versions up to 6.0M3 and Android versions prior to 4.4.
The impact of CVE-2013-7372 includes the potential for attackers to predict cryptographic keys resulting from insecure random number generation.
Yes, CVE-2013-7372 specifically affects the Java Cryptography Architecture (JCA) implementation in Apache Harmony and certain Android versions.