LiveActive security incident?Get immediate response
CVE Record

CVE-2014-0878: The IBMSecureRandom component in the IBMJCE and IBMSecureRandom cryptographic providers in IBM SDK Java Tec...

The IBMSecureRandom component in the IBMJCE and IBMSecureRandom cryptographic providers in IBM SDK Java Technology Edition 5.0 before Service Refresh 16 FP6, 6 before Service Refresh 16, 6.0.1 before Service Refresh 8, 7 before Service Refresh 7, and 7R1 before Service Refresh 1 makes it easier for context-dependent attackers to defeat cryptographic protection mechanisms by predicting the random number generator's output.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2014-0878 is a weakness in IBM Java cryptographic random number generation. In affected IBM SDK Java versions, random values may be predictable, which can undermine encryption, authentication tokens, or keys generated in the wrong context. The sources do not provide CVSS, exploit details, or evidence of active exploitation. Exposure is most likely where affected IBM SDK Java runtimes are installed and applications rely on IBMJCE or IBMSecureRandom providers for keys, tokens, session identifiers, TLS, signing, or encryption workflows. Treat this as a targeted cryptographic hygiene issue rather than a confirmed emergency. Prioritize internet-facing or security-sensitive Java workloads because predictable randomness can invalidate security assumptions, but the source bundle lacks severity scoring and active exploitation evidence. Mitigation focus: Upgrade affected IBM SDK Java versions to the fixed service refresh levels or later.; Check IBM support guidance for product-specific Java runtime update paths.; Inventory embedded IBM Java runtimes inside middleware, appliances, and bundled applications..

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-2014-0878 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
2Source 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.