CVE-2013-0422

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-05-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 4 sources updated this weekExploited in the wild
9.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 98%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
99.9%
KEV
⚠ Exploited

Published

January 10, 2013

Last Modified

April 21, 2026

Advisory Details (6)

Auto-updated Apr 29, 2026
⚠️ Active exploitation confirmed. Patch available.
generic🔴 Active Exploitation

Bugtraq: [SE-2012-01] 'Fix' for Issue 32 exploited by new Java 0-day code

http://seclists.org/bugtraq/2013/Jan/48
generic🔴 Active Exploitation

0 day 1.7u10 (CVE-2013-0422) spotted in the Wild - Disable Java Plugin NOW !

http://malware.dontneedcoffee.com/2013/01/0-day-17u10-spotted-in-while-disable.html
generic Patch Available

Zero-Day Java Exploit Debuts in Crimeware – Krebs on Security

http://krebsonsecurity.com/2013/01/zero-day-java-exploit-debuts-in-crimeware/
generic🔴 Active Exploitation

Immunity Products: Confirmed: Java only fixed one of the two bugs.

http://immunityproducts.blogspot.ca/2013/01/confirmed-java-only-fixed-one-of-two.html

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenjdk-7-jre (7u9-2.3.4-0ubuntu1.12.10.1) @ quantal2026-07-07ubuntu
redhatjava-1.7.0-ibm-1:1.7.0.4.0-1jpp.2.el6_42013-03-11redhat
redhatjava-1.7.0-openjdk-1:1.7.0.9-2.3.4.1.el6_32013-01-16redhat
redhatjava-1.7.0-oracle-1:1.7.0.11-1jpp.3.el6_32013-01-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 124× in last 7d / 545× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 715 total refreshes for this CVE.

  1. 2026-07-07 05:11 UTCEG score recompute
  2. 2026-07-07 05:11 UTCVendor advisory
  3. 2026-07-07 05:10 UTCGHSA enrichment
  4. 2026-07-07 01:04 UTCEG score recompute
  5. 2026-07-07 01:04 UTCVendor advisory
  6. 2026-07-07 01:04 UTCGHSA enrichment
  7. 2026-07-06 20:58 UTCEG score recompute
  8. 2026-07-06 20:58 UTCVendor advisory
  9. 2026-07-06 20:58 UTCGHSA enrichment
  10. 2026-07-06 16:51 UTCEG score recompute
  11. 2026-07-06 16:51 UTCVendor advisory
  12. 2026-07-06 16:51 UTCGHSA enrichment
  13. 2026-07-06 12:46 UTCEG score recompute
  14. 2026-07-06 12:46 UTCVendor advisory
  15. 2026-07-06 12:46 UTCGHSA enrichment
  16. 2026-07-06 08:40 UTCEG score recompute
  17. 2026-07-06 08:40 UTCVendor advisory
  18. 2026-07-06 08:40 UTCGHSA enrichment
  19. 2026-07-06 04:33 UTCEG score recompute
  20. 2026-07-06 04:33 UTCVendor advisory
  21. 2026-07-06 04:33 UTCGHSA enrichment
  22. 2026-07-06 00:27 UTCEG score recompute
  23. 2026-07-06 00:27 UTCVendor advisory
  24. 2026-07-06 00:27 UTCGHSA enrichment
  25. 2026-07-05 20:21 UTCEG score recompute
Show 75 more
  1. 2026-07-05 20:21 UTCVendor advisory
  2. 2026-07-05 20:21 UTCGHSA enrichment
  3. 2026-07-05 16:16 UTCEG score recompute
  4. 2026-07-05 16:16 UTCVendor advisory
  5. 2026-07-05 16:15 UTCGHSA enrichment
  6. 2026-07-05 12:08 UTCEG score recompute
  7. 2026-07-05 12:08 UTCVendor advisory
  8. 2026-07-05 12:08 UTCGHSA enrichment
  9. 2026-07-05 08:02 UTCEG score recompute
  10. 2026-07-05 08:02 UTCVendor advisory
  11. 2026-07-05 08:02 UTCGHSA enrichment
  12. 2026-07-05 03:55 UTCEG score recompute
  13. 2026-07-05 03:55 UTCVendor advisory
  14. 2026-07-05 03:55 UTCGHSA enrichment
  15. 2026-07-04 23:49 UTCEG score recompute
  16. 2026-07-04 23:49 UTCVendor advisory
  17. 2026-07-04 23:49 UTCGHSA enrichment
  18. 2026-07-04 19:43 UTCEG score recompute
  19. 2026-07-04 19:43 UTCVendor advisory
  20. 2026-07-04 19:42 UTCGHSA enrichment
  21. 2026-07-04 15:37 UTCEG score recompute
  22. 2026-07-04 15:37 UTCVendor advisory
  23. 2026-07-04 15:37 UTCGHSA enrichment
  24. 2026-07-04 11:29 UTCEG score recompute
  25. 2026-07-04 11:29 UTCVendor advisory
  26. 2026-07-04 11:29 UTCGHSA enrichment
  27. 2026-07-04 07:24 UTCEG score recompute
  28. 2026-07-04 07:24 UTCVendor advisory
  29. 2026-07-04 07:24 UTCGHSA enrichment
  30. 2026-07-04 03:16 UTCEG score recompute
  31. 2026-07-04 03:16 UTCVendor advisory
  32. 2026-07-04 03:15 UTCGHSA enrichment
  33. 2026-07-03 23:08 UTCEG score recompute
  34. 2026-07-03 23:08 UTCVendor advisory
  35. 2026-07-03 23:08 UTCGHSA enrichment
  36. 2026-07-03 19:01 UTCEG score recompute
  37. 2026-07-03 19:01 UTCVendor advisory
  38. 2026-07-03 19:01 UTCGHSA enrichment
  39. 2026-07-03 14:56 UTCEG score recompute
  40. 2026-07-03 14:56 UTCVendor advisory
  41. 2026-07-03 14:55 UTCGHSA enrichment
  42. 2026-07-03 10:49 UTCEG score recompute
  43. 2026-07-03 10:49 UTCVendor advisory
  44. 2026-07-03 10:49 UTCGHSA enrichment
  45. 2026-07-03 06:42 UTCEG score recompute
  46. 2026-07-03 06:42 UTCVendor advisory
  47. 2026-07-03 06:42 UTCGHSA enrichment
  48. 2026-07-03 02:35 UTCEG score recompute
  49. 2026-07-03 02:35 UTCVendor advisory
  50. 2026-07-03 02:35 UTCGHSA enrichment
  51. 2026-07-02 22:30 UTCEG score recompute
  52. 2026-07-02 22:30 UTCVendor advisory
  53. 2026-07-02 22:30 UTCGHSA enrichment
  54. 2026-07-02 18:25 UTCEG score recompute
  55. 2026-07-02 18:25 UTCVendor advisory
  56. 2026-07-02 18:25 UTCGHSA enrichment
  57. 2026-07-02 14:20 UTCEG score recompute
  58. 2026-07-02 14:20 UTCVendor advisory
  59. 2026-07-02 14:20 UTCGHSA enrichment
  60. 2026-07-02 10:14 UTCEG score recompute
  61. 2026-07-02 10:14 UTCVendor advisory
  62. 2026-07-02 10:14 UTCGHSA enrichment
  63. 2026-07-02 06:09 UTCEG score recompute
  64. 2026-07-02 06:09 UTCVendor advisory
  65. 2026-07-02 06:09 UTCGHSA enrichment
  66. 2026-07-02 02:03 UTCEG score recompute
  67. 2026-07-02 02:03 UTCVendor advisory
  68. 2026-07-02 02:03 UTCGHSA enrichment
  69. 2026-07-01 21:58 UTCEG score recompute
  70. 2026-07-01 21:58 UTCVendor advisory
  71. 2026-07-01 21:58 UTCGHSA enrichment
  72. 2026-07-01 19:16 UTCCISA KEV update
  73. 2026-07-01 17:51 UTCEG score recompute
  74. 2026-07-01 17:51 UTCVendor advisory
  75. 2026-07-01 17:51 UTCGHSA enrichment

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-24045✓ verified
    First seen Jan 11, 2013

    Java Applet JMX - Remote Code Execution (Metasploit) (1)

    Open source ↗
  • Metasploitexploit/multi/browser/java_jre17_jmxbean✓ verified
    First seen Jan 10, 2013

    Java Applet JMX Remote Code Execution

    Open source ↗

Frequently asked(6)

What is CVE-2013-0422?
CVE-2013-0422 is a critical vulnerability published on January 10, 2013. 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…
When was CVE-2013-0422 disclosed?
CVE-2013-0422 was first published in the National Vulnerability Database on January 10, 2013, with the most recent update on April 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-0422 actively exploited?
Yes. CISA added CVE-2013-0422 to the Known Exploited Vulnerabilities catalog on May 25, 2022, affecting Oracle Java Runtime Environment (JRE). KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2013-0422?
CVE-2013-0422 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2013-0422?
CVE-2013-0422 affects Oracle Java Runtime Environment (JRE). The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2013-0422?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-0422, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2013-0422

Explore →

Is Your Infrastructure Affected by CVE-2013-0422?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.