CVE-2015-2342

HIGHCVSS v2 · 10.010.0
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; 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% exploitation probability in the next 30 days; it does not lift the v2 base. EPSS sets EG Risk's exploitation input. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
Weaponized
10.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 89%
  • Public exploit code is available (Metasploit, Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 89%CVSS v2: 10.0Exploit: Metasploit · Exploit-DB (verified)Exposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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.0HIGHlow confidence
EG Risk
81
EG Risk 81/100

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 (value × EchelonGraph’s weight)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation89% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
89%
EPSS %ILE
99th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 12, 2015

Last Modified

May 6, 2026

Data Freshness Timeline

(refreshed 3× in last 7d / 8× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 4,442 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 4,343 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (2 Metasploit modules, 1 Exploit-DB entry). No release with the fix is confirmed, so defenders should restrict or isolate affected systems accordingly until one is applied.

  • Metasploitauxiliary/scanner/misc/java_jmx_server✓ verified
    Published Dec 19, 2018

    Java JMX Server Insecure Endpoint Code Execution Scanner

    Open source ↗
  • Exploit-DBEDB-36101✓ verified
    Published Feb 17, 2015

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

    Open source ↗
  • Metasploitexploit/multi/misc/java_jmx_server✓ verified
    Published Feb 17, 2015

    Java JMX Server Insecure Configuration Java Code Execution

    Open source ↗

Frequently asked(4)

What is CVE-2015-2342?
CVE-2015-2342 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2015-2342 was made public on October 1, 2015: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on October 12, 2015. EchelonGraph's copy of the record carries a last-modified date of May 6, 2026; the record at its source may have been updated since.
Is CVE-2015-2342 actively exploited?
CVE-2015-2342 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 89% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2015-2342?
A fix for CVE-2015-2342 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

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.