LiveActive security incident?Get immediate response
CVE Record

CVE-2013-1571: Unspecified vulnerability in the Javadoc component in Oracle Java SE 7 Update 21 and earlier, 6 Update 45 a...

Unspecified vulnerability in the Javadoc component in Oracle Java SE 7 Update 21 and earlier, 6 Update 45 and earlier, and 5.0 Update 45 and earlier; JavaFX 2.2.21 and earlier; and OpenJDK 7 allows remote attackers to affect integrity via unknown vectors related to Javadoc. NOTE: the previous information is from the June 2013 CPU. Oracle has not commented on claims from another vendor that this issue is related to frame injection in HTML that is generated by Javadoc.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old Oracle Java Javadoc vulnerability with limited public detail. The record says remote attackers could affect integrity in Java SE, JavaFX, and OpenJDK versions current before June 2013. No CVSS score or active exploitation evidence is provided. Exposure is most likely in legacy systems, build environments, or documentation pipelines still using the listed Java/Javadoc versions, or in public documentation generated by them. Modern supported Java installations are less likely to be affected if vendor security updates were applied. Prioritize as a legacy technology hygiene issue. Urgency rises where obsolete Java remains in production, build pipelines, or publicly served documentation. The public record lacks severity scoring and exploitation evidence, so prioritize by asset criticality and exposure. Mitigation focus: Inventory Java SE, JavaFX, OpenJDK, and build images for the listed affected versions.; Apply vendor security updates from Oracle or your operating system vendor advisories.; Retire unsupported Java 5, 6, and 7 runtimes where business dependencies allow..

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-1571 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
14Source 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.