Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2013-1493: Remote Code Execution in Oracle Java SE Color Management

Published Mar 4, 2013 · Updated 15 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v2
EPSS86.2%100th percentile
CISA KEVNoNot listed
In the wildReported10 exploitation records in Mallory
Vendors
SunOracle Corporation
IdentifiersCVE-2013-1493CWE-119 · Improper Restriction of Operations…

CVE-2013-1493 is a memory-safety vulnerability in the color management (CMM) functionality of Oracle Java SE's 2D component. Processing an image with crafted raster parameters can trigger an out-of-bounds read or memory corruption in the Java Virtual Machine, enabling arbitrary code execution or a crash. Affected releases include Java SE 7 Update 15 and earlier, Java SE 6 Update 41 and earlier, and Java SE 5.0 Update 40 and earlier. The vulnerability was exploited in the wild in February 2013 and subsequently incorporated into multiple exploit kits.

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, unauthenticated attacker can execute arbitrary code with the privileges of the affected Java process or cause denial of service by crashing the JVM. Browser-based exploitation can compromise the user's system through malicious Java content. Observed exploitation delivered ransomware and remote-access malware, including Exxroute, 9002 RAT, and Poison Ivy. Exploitation does not inherently establish operating-system privilege escalation beyond the compromised process's privileges.

Mitigation

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

Disable Java browser integration wherever it is unnecessary. In Java 7 Update 10 and later, deselect "Enable Java content in the browser" on the Java Control Panel Security tab to prevent both signed and unsigned Java applications from running in browsers. Remove or disable unnecessary Java plug-ins, Java Deployment Toolkit functionality, and Java Web Start to reduce alternate delivery paths. Disabling browser integration alone does not protect standalone Java applications that process attacker-controlled images.

Remediation

Patch, then assume compromise.

Apply Oracle's March 2013 security update addressing CVE-2013-1493: Java 7 Update 17 or Java 6 Update 43 were the historical fixed releases. For current deployments, replace these obsolete Java branches with a supported, fully patched release. Update all installed JRE and JDK instances, including application-bundled runtimes. For affected OpenJDK, IcedTea, or vendor-bundled Java distributions, install the corresponding vendor security update. A specific fixed Java 5 release is not identified.

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-1493 exploited in the wild?
Yes. As of Nov 2, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2013-1493?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2013-1493, the earliest disclosed Mar 1, 2013.
Is there a patch for CVE-2013-1493?
Apply Oracle's March 2013 security update addressing CVE-2013-1493: Java 7 Update 17 or Java 6 Update 43 were the historical fixed releases. For current deployments, replace these obsolete Java branches with a supported, fully patched release.
What products are affected by CVE-2013-1493?
Sun Jdk, Oracle Corporation Jdk, Sun Jre, and Oracle Corporation Jre.
How severe is CVE-2013-1493?
CVE-2013-1493 has a CVSS v2 score of 10.0 (Critical) and an EPSS score of 86.2% (100th percentile) as of Nov 2, 2026.
Activity feed

Recent activity

11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+5 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 evidence1Every report linking this CVE to a named adversary.
Associated malware6Malware 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.