CVE-2013-0422 — Oracle JRE Remote Code Execution Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Used in ransomware campaigns (CISA)+10
- Public exploit/PoC (metasploit, exploitdb)+20
- EPSS 97% (30-day exploitation probability)+15
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
CISA required action CISA
Apply updates per vendor instructions.
US federal deadline: Jun 15, 2022 — passed 1584 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Canonical Ubuntu Linux, Opensuse Opensuse, Oracle Jdk…).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Canonical | Ubuntu Linux | version 12.10 | Vulnerable | NIST National Vulnerability Database |
| Opensuse | Opensuse | version 12.2 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Jdk |
version 1.7.0-update9version 1.7.0-update7version 1.7.0-update6version 1.7.0-update5version 1.7.0-update4version 1.7.0-update3version 1.7.0-update2version 1.7.0-update10 and 2 moreversion 1.7.0-update1version 1.7.0 |
Vulnerable | NIST National Vulnerability Database |
| Oracle | Jre |
version 1.7.0version 1.7.0-update1version 1.7.0-update10version 1.7.0-update2version 1.7.0-update3version 1.7.0-update4version 1.7.0-update5version 1.7.0-update6 and 2 moreversion 1.7.0-update7version 1.7.0-update9 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 9.8 | CVSS 3.1 | Critical | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
| 10.0 | CVSS 2.0 | High | 10.0 | 10.0 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- Java Applet JMX Remote Code Execution excellent Jan 10, 2013
- Java Applet JMX - Remote Code Execution (Metasploit) (1) verified Jan 11, 2013
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 97.02%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
- Hunt retroactively in logs from before May 25, 2022 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · oracle/jdk, oracle/jre, canonical/ubuntu linux, opensuse/opensuse
- Source status changed · Published → Analyzed
- Record published
- CVSS changed · 9.8
- Source status changed · → Published
- SSVC assessment updated
- Added to CISA KEV (detected)
- Record created in this database
- 2022
- Added to CISA KEV catalog
- 2013
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 3× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
25 on the record
- www.oracle.com/technetwork/topics/security/alert-cve-2013-0422-1896849.html
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- rhn.redhat.com/errata/RHSA-2013-0156.html
- threatpost.com/en_us/blogs/nasty-new-java-zero-day-found-exploit-kits-already-have-i
- rhn.redhat.com/errata/RHSA-2013-0165.html
- partners.immunityinc.com/idocs/Java%20MBeanInstantiator.findClass%200day%20Analysis.pdf
- krebsonsecurity.com/2013/01/zero-day-java-exploit-debuts-in-crimeware/
- www.kb.cert.org/vuls/id/625617
- krebsonsecurity.com/2013/01/zero-day-java-exploit-debuts-in-crimeware
- labs.alienvault.com/labs/index.php/2013/new-year-new-java-zeroday/
- malware.dontneedcoffee.com/2013/01/0-day-17u10-spotted-in-while-disable.html
- blog.fuseyism.com/index.php/2013/01/15/security-icedtea-2-1-4-2-2-4-2-3-4-released
- wiki.mageia.org/en/Support/Advisories/MGASA-2013-0018
- seclists.org/bugtraq/2013/Jan/48
- blog.fuseyism.com/index.php/2013/01/15/security-icedtea-2-1-4-2-2-4-2-3-4-released/
- lists.opensuse.org/opensuse-security-announce/2013-01/msg00025.html
- github.com/advisories/GHSA-r293-6mhc-29xx
- immunityproducts.blogspot.ca/2013/01/confirmed-java-only-fixed-one-of-two.html
- labs.alienvault.com/labs/index.php/2013/new-year-new-java-zeroday
- nvd.nist.gov/vuln/detail/CVE-2013-0422
- blog.fireeye.com/research/2013/01/happy-new-year-from-new-java-zero-day.html
- www.mandriva.com/security/advisories
- www.ubuntu.com/usn/USN-1693-1
- www-304.ibm.com/connections/blogs/PSIRT/entry/oracle_java_7_security_manager_bypass_v
- www.us-cert.gov/cas/techalerts/TA13-010A.html
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-62574 Improper Access Control in Oracle Jre Jul 21, 2026
- Medium CVE-2026-60526 Improper Input Validation in Oracle Jdk Jul 21, 2026
- Low CVE-2026-60166 Vulnerability in Oracle Java SE (component: JavaFX). The supported version that is… Jul 21, 2026
- Low CVE-2026-60164 Vulnerability in Oracle Java SE (component: JavaFX). The supported version that is… Jul 21, 2026
- Medium CVE-2026-60147 Improper Access Control in Oracle Jre Jul 21, 2026
- High CVE-2026-47063 Improper Access Control in Oracle Jre Jul 21, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2013-0422 is "Oracle JRE Remote Code Execution Vulnerability", rated Critical. It affects Ubuntu Linux (Canonical); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 97.02% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.