LiveActive security incident?Get immediate response
CVE Record

CVE-2013-1475: Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Updat...

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11, 6 through Update 38, 5.0 through Update 38, and 1.4.2_40 and earlier, and OpenJDK 6 and 7, allows remote attackers to affect confidentiality, integrity, and availability via vectors related to CORBA. NOTE: the previous information is from the February 2013 CPU. Oracle has not commented on claims from another vendor that this issue is related to "IIOP type reuse management" in ObjectStreamClass.java.

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

Security readout for executives and security teams

CVE-2013-1475 is an old Java runtime flaw tied to CORBA processing. The public record says remote attackers could affect confidentiality, integrity, and availability, but details and severity scoring are incomplete. The practical risk is concentrated in legacy Java and OpenJDK 6/7 deployments that have not received 2013-era security updates. Exposure is most likely where obsolete Oracle Java SE or OpenJDK 6/7 runtimes remain installed on servers, desktops, or packaged applications. Systems using vendor-patched distributions after the February 2013 CPU are less likely to be exposed, but asset verification is required. Prioritize this during legacy Java risk reduction. It is not flagged as known exploited in the provided sources, but unsupported Java runtimes create broad operational and security exposure beyond this single CVE. Mitigation focus: Inventory Java and OpenJDK versions across servers, endpoints, and bundled applications.; Apply relevant Oracle, OpenJDK, or Linux distribution security updates from the cited advisories.; Remove unsupported Java 1.4, 5, 6, and early 7 runtimes where possible..

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-1475 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.