LiveActive security incident?Get immediate response
CVE Record

CVE-2013-7372: The engineNextBytes function in classlib/modules/security/src/main/java/common/org/apache/harmony/security/...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

A flawed random-number generator in Apache Harmony, used by Android before 4.4, could produce predictable cryptographic values when applications did not supply their own seed. That can undermine keys, signatures, and wallet security. Public sources tie this weakness to Bitcoin wallet losses in August 2013. Exposure is most likely in legacy Android applications or products using Apache Harmony SecureRandom behavior before Android 4.4, especially where cryptographic keys, signatures, wallets, or tokens were generated without explicit secure seeding. Prioritize if the organization still supports legacy Android, embedded Java stacks, or wallets using keys generated on affected systems. The main business risk is compromise of cryptographic trust, including irreversible asset theft or invalidated authentication. Mitigation focus: Move affected Android environments and applications off pre-4.4 SecureRandom behavior using vendor guidance.; Check whether applications bundle Apache Harmony crypto classes and update or replace them if affected.; For wallet exposure, follow wallet/vendor guidance for moving assets to keys generated by fixed software..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2013-7372 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.