LiveActive security incident?Get immediate response
CVE Record

CVE-2013-5910: Unspecified vulnerability in Oracle Java SE 6u65 and 7u45, Java SE Embedded 7u45, and OpenJDK 7 allows remo...

Unspecified vulnerability in Oracle Java SE 6u65 and 7u45, Java SE Embedded 7u45, and OpenJDK 7 allows remote attackers to affect integrity via unknown vectors related to Security. NOTE: the previous information is from the January 2014 CPU. Oracle has not commented on third-party claims that CanonicalizerBase.java in the XML canonicalizer allows untrusted code to access mutable byte arrays.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old Java vulnerability from Oracle's January 2014 update cycle. The public record says remote attackers could affect integrity, but the attack path and severity are not documented in the provided sources. Treat it as a legacy Java exposure: important where affected Java 6, Java 7, Java Embedded, or OpenJDK 7 still exists. Exposure is most likely on systems still running the listed 2014-era Java or OpenJDK 7 versions. Any application, endpoint, server, appliance, or embedded environment using those runtimes may be relevant. The sources do not define a narrower affected configuration. Make this a legacy technology cleanup priority. Urgency rises if affected Java versions remain on externally reachable systems, security-sensitive applications, or embedded platforms that are hard to monitor. The lack of detail limits scoring, but the age of the runtimes is itself a business risk. Mitigation focus: Identify and remove affected Java SE 6, Java SE 7, Java Embedded, and OpenJDK 7 runtimes.; Apply the relevant 2014 vendor security updates where legacy runtimes cannot be removed.; Check Oracle, Red Hat, Ubuntu, SUSE, or platform vendor guidance for package-specific fixes..

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-5910 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
5Source 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.