Microsoft Security
CVE-2013-0422 first appeared in January 2013 as a zero-day vulnerability.
4 passages name itOriginal (opens in a new tab) ↗
Oracle · Java Runtime Environment (JRE)
End of lifeJava SE 6/7 reached End of lifeThe vendor no longer ships security fixes. Remove or isolate the product instead of waiting for a patch. on 14 Apr 2015. No patch is coming: remove or isolate it.
The Oracle Java Runtime Environment (JRE) contains multiple flaws in Oracle Java 7 before Update 11, in the JMX MBean instantiation path (JmxMBeanServer.getMBeanInstantiator and findClass) and in the Reflection API's handling of security checks through MethodHandles.Lookup.checkSecurityManager and Reflection.getCallerClass. A remote attacker with no privileges and no user interaction beyond reaching the vulnerable Java code can execute arbitrary code, and the Reflection API vector is known to have been used in attacks.
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.
First seen exploited the day it was disclosed. Public exploit code (Metasploit) was available the same day.
CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.
arbitrary code execution in the Java context
allow remote attackers to execute arbitrary code
These come from early or generic mappings, text matching, or contradict this CVE’s details (for example a public-facing technique on a bug that needs a user to open a file). Shown for completeness.
CVE-specific rules are not available in this build. Search SigmaHQ ↗
These detect the technique in general, not this specific vulnerability.
Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.
Reports are matched by finding the exact id CVE-2013-0422 in their text; nobody has reviewed the match. One passage is shown per report, at most 320 characters, linked to the original.
CVE-2013-0422 first appeared in January 2013 as a zero-day vulnerability.
4 passages name itOriginal (opens in a new tab) ↗
CVE-2013-0422 first appeared in January 2013 as a zero-day vulnerability.
4 passages name itOriginal (opens in a new tab) ↗
Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.