CVE-2013-0422
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.
In plain language
AI Act nowCVE-2013-0422 is a critical remote code execution bug in older Oracle Java 7 releases (before Update 11); if your business runs Java 7 that’s not fully updated, you should treat this as an urgent risk.
CVE-2013-0422 (KEV) covers multiple remote code execution weaknesses in Oracle Java 7 before Update 11, including misuse of the JMX MBean instantiation path and a Reflection API security-check bypass; attackers can run code without needing local access, and it has been used in real-world ransomware campaigns.
What to do now
- Check whether any system in your business is running Oracle Java 7 (look for “1.7” in your Java version output) and whether it is older than “Update 11”.
- If Java 7 is present and older than Update 11, plan an immediate upgrade to Oracle Java 7 Update 11 or later using your vendor’s supported method (for managed Linux packages, upgrade the Java/JRE packages that your OS vendor provides).
- If you cannot upgrade right away, temporarily disable or restrict Java 7 usage for internet-facing services (e.g., stop services that use that Java version and prevent remote access to those services) until the update is applied.
- Confirm after updating that the Java version is Update 11 or later and review web/app server logs for suspicious activity related to Java/JMX/Reflection exploitation patterns.
CVSS Vector Breakdown
AV:NAttack VectorAC:LAttack ComplexityPR:NPrivileges RequiredUI:NUser InteractionS:UScopeC:HConfidentialityI:HIntegrityA:HAvailabilityWeaknesses
Affected Products
Exploitability
Required action: Apply updates per vendor instructions.
References
Unlock Complete Vulnerability Intelligence
Get the full picture for CVE-2013-0422 and every CVE in our database. Create a free account — no credit card required.
Create Free Account