CVE-2015-2342

HIGHCVSS v2 · 10.010.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 89.0% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
10.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 89%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 89%CVSS v2: 10.0Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The JMX RMI service in VMware vCenter Server 5.0 before u3e, 5.1 before u3b, 5.5 before u3, and 6.0 before u1 does not restrict registration of MBeans, which allows remote attackers to execute arbitrary code via the RMI protocol.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0(low)
EG Risk
85(Track)
EG Risk 85/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation89% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
89%
EPSS %ILE
100%
KEV
Not listed

Published

October 12, 2015

Last Modified

May 6, 2026

References (12)

Data Freshness Timeline

(refreshed 1× in last 7d / 4394× 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 4,427 total refreshes for this CVE.

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

Publicly available exploits

(3 references)

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

  • Exploit-DBEDB-36101✓ verified
    First seen Feb 17, 2015

    Java JMX - Server Insecure Configuration Java Code Execution (Metasploit)

    Open source ↗
  • Metasploitauxiliary/scanner/misc/java_jmx_server✓ verified
    First seen May 22, 2013

    Java JMX Server Insecure Endpoint Code Execution Scanner

    Open source ↗
  • Metasploitexploit/multi/misc/java_jmx_server✓ verified
    First seen May 22, 2013

    Java JMX Server Insecure Configuration Java Code Execution

    Open source ↗

Frequently asked(4)

What is CVE-2015-2342?
CVE-2015-2342 is a high vulnerability published on October 12, 2015. The JMX RMI service in VMware vCenter Server 5.0 before u3e, 5.1 before u3b, 5.5 before u3, and 6.0 before u1 does not restrict registration of MBeans, which allows remote attackers to execute arbitrary code via the RMI protocol.
When was CVE-2015-2342 disclosed?
CVE-2015-2342 was first published in the National Vulnerability Database on October 12, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-2342 actively exploited?
CVE-2015-2342 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 89% probability of exploitation in the next 30 days, which ranks it in the top 0.2% of all scored CVEs.
How do I remediate CVE-2015-2342?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-2342, 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-2015-2342

Explore →

Is Your Infrastructure Affected by CVE-2015-2342?

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

Start Free Scan →Browse All CVEs