Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2013-0422: Java 7 SecurityManager Bypass and Remote Code Execution

Published Jan 10, 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.
CVSS9.8Critical · v3.1
EPSS97.1%100th percentile
CISA KEVYesAdded May 25, 2022
In the wildActivePer CISA KEV
Vendors
Oracle CorporationOpensuseCanonical
IdentifiersCVE-2013-0422CWE-863

CVE-2013-0422 encompasses JMX/MBean and recursive Reflection API vulnerabilities that allow untrusted Java code to bypass SecurityManager restrictions in Oracle Java 7 Update 10 and earlier. The JMX vector uses JmxMBeanServer.getMBeanInstantiator to access a private MBeanInstantiator object, then calls findClass to obtain arbitrary class references. The reflection vector bypasses MethodHandles.Lookup.checkSecurityManager because Reflection.getCallerClass does not correctly skip frames associated with the newer reflection API. Malicious applets can consequently execute arbitrary code outside their intended sandbox. OpenJDK 7 and IcedTea 2.x are also affected; the initial claim that Java 6 was exploitable was retracted. Exploitation occurred in the wild in January 2013, including through Blackhole and Nuclear Pack.

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.

Remote, unauthenticated attackers can execute arbitrary code with the privileges of the Java plug-in process and its user, compromising confidentiality, integrity, and availability within those privileges. Exposure includes malicious applets delivered through web pages, Java Web Start applications, and applications embedding Internet Explorer rendering components, including Microsoft Office and Windows Desktop Search. Successful exploitation can enable malware installation and unauthorized commands without requiring a separately established privileged account.

Mitigation

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

Disable Java content in browsers unless required, including after installing Java 7 Update 11, and uninstall unused Java installations. Java 7 Update 10 and later support browser-content disabling through the Java Control Panel or the WEB_JAVA=0 installation option. If browser Java must remain enabled, restrict Java archive and class downloads and Java User-Agent requests through proxy controls, allowing only required trusted destinations. Do not rely solely on security prompts: disabling and subsequently re-enabling Java was associated with Internet Explorer prompt-bypass behavior on Windows 7 and Vista.

Remediation

Patch, then assume compromise.

Apply the appropriate vendor security update. Oracle released Java 7 Update 11 to address CVE-2013-0422 and the separate CVE-2012-3174; fixed IcedTea releases include 2.1.4, 2.2.4, and 2.3.4 for their respective branches. However, contemporary third-party analysis disputed the completeness of Update 11, reporting that the reflection issue was fixed while the JMX/MBean issue remained. Retain browser-Java restrictions after patching and use a currently supported, fully updated Java release rather than relying on the historical Update 11 baseline.

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
CanonicalUbuntu Linuxoperating_system
OpensuseOpensuseoperating_system
Oracle CorporationJdkapplication
Oracle CorporationJreapplication
FAQ

Frequently asked questions

Is CVE-2013-0422 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on May 25, 2022.
Is there a public exploit for CVE-2013-0422?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2013-0422, the earliest disclosed Jan 10, 2013.
Is there a patch for CVE-2013-0422?
Apply the appropriate vendor security update. Oracle released Java 7 Update 11 to address CVE-2013-0422 and the separate CVE-2012-3174; fixed IcedTea releases include 2.1.4, 2.2.4, and 2.3.4 for their respective branches.
What products are affected by CVE-2013-0422?
Oracle Corporation Jdk, Oracle Corporation Jre, Opensuse, and Canonical Ubuntu Linux.
How severe is CVE-2013-0422?
CVE-2013-0422 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 97.1% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

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

View more in app →
+7 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 evidence2Every report linking this CVE to a named adversary.
Associated malware10Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.