LiveActive security incident?Get immediate response
CVE Record

CVE-2013-2470: Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 21 and...

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 21 and earlier, 6 Update 45 and earlier, and 5.0 Update 45 and earlier, and OpenJDK 7, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D. NOTE: the previous information is from the June 2013 CPU. Oracle has not commented on claims from another vendor that this issue allows remote attackers to bypass the Java sandbox via vectors related to "ImagingLib byte lookup processing."

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

Security readout for executives and security teams

CVE-2013-2470 is an old Java Runtime vulnerability in Oracle Java SE and OpenJDK 7. The public record says remote attackers could affect confidentiality, integrity, and availability through the 2D component. A vendor also claimed a Java sandbox bypass related to ImagingLib byte lookup processing, but Oracle did not comment on that claim. Exposure is most likely where legacy Java runtimes remain installed, especially Oracle Java SE 5, 6, or 7 at affected update levels, or OpenJDK 7 packages that missed vendor security updates. Modern systems without those runtimes are unlikely to be affected based on the provided record. Prioritize remediation when legacy Java is present on user endpoints, application servers, or managed images. The age of the issue reduces surprise risk, but unsupported Java often persists in business applications and can create avoidable exposure with limited detection detail. Mitigation focus: Apply Oracle June 2013 CPU or later vendor Java security updates.; Update affected OpenJDK 7 packages using the relevant OS vendor advisory.; Retire unsupported Java 5, 6, or 7 runtimes where updates are unavailable..

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-2470 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
7Source 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.