# CVE-2013-0422: Oracle JRE Remote Code Execution > Remote attackers can execute arbitrary code by bypassing Java security checks via JMX and Reflection API flaws, requiring an upgrade to Java 7 Update 11. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Yes, since 25 May 2022 (CISA KEV), used in ransomware - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Jan 2013 - **Updated:** 22 Oct 2025 - **Also known as:** GHSA-r293-6mhc-29xx ## What is CVE-2013-0422? CVE-2013-0422 is a critical vulnerability in Canonical Ubuntu Linux, published on 10 Jan 2013. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2013-0422? It affects 4 products. Products: Canonical Ubuntu Linux, Opensuse Opensuse, Oracle Jdk, Oracle Jre. ## How do I fix CVE-2013-0422? Upgrade to a fixed version. US federal agencies must fix it by 15 Jun 2022. ## Is CVE-2013-0422 being exploited? Yes. Attackers have exploited CVE-2013-0422 in the wild since at least 25 May 2022, including in ransomware campaigns. Public exploit code: - Java Applet JMX Remote Code Execution (metasploit) - Java Applet JMX - Remote Code Execution (Metasploit) (1) (exploitdb) ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2013-0422 and fix it if it is affected. What it is: CVE-2013-0422 is a critical vulnerability in Canonical Ubuntu Linux, published on 10 Jan 2013. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: Yes. Attackers have exploited CVE-2013-0422 in the wild since at least 25 May 2022, including in ransomware campaigns. Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2013-0422/ (Markdown: https://insights.sbomify.com/CVE-2013-0422/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2013-0422 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-0422 - OSV: https://osv.dev/vulnerability/CVE-2013-0422 --- From sbomify Insights: https://insights.sbomify.com/CVE-2013-0422/ Summaries are generated and may contain mistakes; the official description above is the record.