CVE-2013-0422

Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using the public…

Browse: All 2013 CVEs · All vendors

CVSS score
9.8 Critical
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CISA KEV
Yes — actively exploited (added 2022-05-25, remediation due 2022-06-15)
Ransomware
Known ransomware campaign use
Weakness (CWE)
NVD-CWE-Other, CWE-284
Published
2013-01-10
Last modified
2026-06-16
NVD status
Analyzed

Description

Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using the public getMBeanInstantiator method in the JmxMBeanServer class to obtain a reference to a private MBeanInstantiator object, then retrieving arbitrary Class references using the findClass method, and (2) using the Reflection API with recursion in a way that bypasses a security check by the java.lang.invoke.MethodHandles.Lookup.checkSecurityManager method due to the inability of the sun.reflect.Reflection.getCallerClass method to skip frames related to the new reflection API, as exploited in the wild in January 2013, as demonstrated by Blackhole and Nuclear Pack, and a different vulnerability than CVE-2012-4681 and CVE-2012-3174. NOTE: some parties have mapped the recursive Reflection API issue to CVE-2012-3174, but CVE-2012-3174 is for a different vulnerability whose details are not public as of 20130114. CVE-2013-0422 covers both the JMX/MBean and Reflection API issues. NOTE: it was originally reported that Java 6 was also vulnerable, but the reporter has retracted this claim, stating that Java 6 is not exploitable because the relevant code is called in a way that does not bypass security checks. NOTE: as of 20130114, a reliable third party has claimed that the findClass/MBeanInstantiator vector was not fixed in Oracle Java 7 Update 11. If there is still a vulnerable condition, then a separate CVE identifier might be created for the unfixed issue.

Affected products

Affected ranges per NVD CPE data; confirm exact versions in the vendor advisory.

Required action (CISA)

Apply updates per vendor instructions. Federal remediation deadline: 2022-06-15.

How to prioritize this

This vulnerability is on the CISA KEV list, meaning it is being actively exploited — treat it as urgent regardless of the raw CVSS number. Use the live CVE lookup for the latest NVD data, and the CVSS 3.1 calculator to model your own environmental score. For the actively exploited vulnerabilities that matter this week, read The Exploit HQ daily security brief.

References

FAQ

Is CVE-2013-0422 actively exploited?

Yes. CISA added CVE-2013-0422 to its Known Exploited Vulnerabilities (KEV) catalog on 2022-05-25, with a federal remediation deadline of 2022-06-15. A KEV listing means real-world exploitation is confirmed, so patching this should be prioritized above many higher-CVSS bugs that aren't being exploited.

What is the CVSS score of CVE-2013-0422?

CVE-2013-0422 has a CVSS base score of 9.8 (Critical). Its vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Related vulnerabilities

Data source: NVD & CISA KEV. Shown as-is; nothing added. Last generated from NVD data — re-check the live tool for updates.