Skip to content
Server Security Center
KEVcritical9.8 Used in ransomware campaigns

CVE-2013-0422: Oracle JRE Remote Code Execution

Oracle Java Runtime Environment (JRE) · listed in the CISA catalog of actively exploited vulnerabilities since 2022-05-25.

CVSS v3.1 (CISA ADP)
9.8
critical
EPSS (exploit probability, 30 days)
97%
higher than 99.8% of all CVEs
Added to CISA KEV
2022-05-25
US federal due date 2022-06-15
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2013-0422 explained

CVE-2013-0422 is a remote code execution vulnerability in Oracle Java Runtime Environment (JRE), described as affecting Oracle Java 7 before Update 11. It covers two flaws that bypass Java security checks. It was exploited in the wild in January 2013, is in CISA's Known Exploited Vulnerabilities catalog and is known to be used in ransomware campaigns.

Impact

Remote attackers can execute arbitrary code on systems running a vulnerable JRE. The CVSS vector describes a network attack with low complexity, no privileges and no user interaction, with high impact on confidentiality, integrity and availability. CISA rates it automatable with total technical impact, meaning attackers can exploit it at scale and gain full control of the affected component. The description notes exploitation through the Blackhole and Nuclear Pack exploit kits.

Who is affected

The CVE record lists Oracle Java Runtime Environment (JRE) but gives no affected versions. The description states that Oracle Java 7 before Update 11 is affected. A claim that Java 6 was vulnerable was retracted by the reporter. The CVE record names no fixed version. Note that, as of 20130114, a third party claimed the MBeanInstantiator vector was not fully fixed in Java 7 Update 11.

Written with AI from the data on this page and checked against it automatically.

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.

CISA required action: Apply updates per vendor instructions.

CISA notes

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: oracle.com/technetwork/topics/security/alert-cve-2013-042…
  • CISA's deadline for US federal agencies: 2022-06-15 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply updates per Oracle's vendor instructions, as CISA requires; Java 7 Update 11 or later is the minimum per the description.
  2. Inventory all systems with Oracle JRE installed, including outdated Java 7 installations.
  3. Remove Java from systems and browsers that do not need it.
  4. Check systems that ran vulnerable Java versions for signs of compromise, including ransomware activity.
  5. Follow the Oracle advisory for any later fixes covering remaining issues.

The CVE record names no fixed version. Follow Oracle's advisory and CISA's required action to apply updates per vendor instructions. The description indicates the issue affects Java 7 before Update 11, so move to a current, supported Java release. Until updated, remove or disable Java where it is not required and limit exposure to untrusted content.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-284 Improper Access Control

Questions about CVE-2013-0422

Is CVE-2013-0422 actively exploited?
Yes. The description states it was exploited in the wild in January 2013 via the Blackhole and Nuclear Pack exploit kits. CISA lists it as a known exploited vulnerability with known ransomware use.
Is Java 6 affected?
The original report said Java 6 was vulnerable, but the reporter retracted this, stating Java 6 is not exploitable because the relevant code does not bypass security checks.
What deadline did CISA set?
CISA added the vulnerability to its catalog on 2022-05-25 with a US federal due date of 2022-06-15. The required action is to apply updates per vendor instructions.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.