Skip to main content
Mallory
CriticalVulnerability

CVE-2013-2471: Oracle Java 2D Unspecified Vulnerability

Published Jun 18, 2013 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v2
EPSS15.0%97th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendors
SunOracle Corporation
IdentifiersCVE-2013-2471CWE-20

CVE-2013-2471 is an unspecified vulnerability in the Java Runtime Environment 2D component affecting Oracle Java SE 7 Update 21 and earlier, Java SE 6 Update 45 and earlier, Java 5.0 Update 45 and earlier, and OpenJDK 7. Oracle described the issue as remotely exploitable through unknown vectors related to Java 2D. A third-party claim associated the flaw with insufficient size checks in IntegerComponentRaster and alleged Java sandbox bypass, but Oracle did not confirm that characterization.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote attacker may affect the confidentiality, integrity, and availability of a vulnerable Java runtime. The claimed sandbox-bypass impact was not confirmed by Oracle.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable the Java browser plugin and prevent untrusted Java content from executing in browsers. Restrict or remove Java from endpoints that do not require it, enforce click-to-play or equivalent browser controls, and use application allowlisting and endpoint controls to block delivery of malicious applets or exploit-kit payloads. Network filtering and web proxy controls can reduce exposure to exploit-kit landing pages, but they are compensating controls only.

Remediation

Patch, then assume compromise.

Apply Oracle's June 2013 CPU or later fixed Java releases, and upgrade affected Oracle Java SE or OpenJDK installations to a version that addresses CVE-2013-2471. Remove or replace unsupported legacy Java 5/6/7 runtimes where possible. Because the issue was actively incorporated into multiple exploit kits, prioritizing patching on Internet-exposed and end-user systems was warranted.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Oracle CorporationJdkapplication
Oracle CorporationJreapplication
SunJdkapplication
SunJreapplication
FAQ

Frequently asked questions

Is CVE-2013-2471 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2013-2471?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2013-2471.
Is there a patch for CVE-2013-2471?
Apply Oracle's June 2013 CPU or later fixed Java releases, and upgrade affected Oracle Java SE or OpenJDK installations to a version that addresses CVE-2013-2471. Remove or replace unsupported legacy Java 5/6/7 runtimes where possible.
What products are affected by CVE-2013-2471?
Sun Jdk, Oracle Corporation Jdk, Sun Jre, and Oracle Corporation Jre.
How severe is CVE-2013-2471?
CVE-2013-2471 has a CVSS v2 score of 10.0 (Critical) and an EPSS score of 15.0% (97th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.