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.
Loading...
Loading...
Score elevated to 9.0 because EPSS predicts 92% probability of exploitation within the next 30 days (top 0.3% of all CVEs). Confidence: see factors.
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.
October 12, 2015
May 6, 2026
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.
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.
Java JMX - Server Insecure Configuration Java Code Execution (Metasploit)
Open source ↗Java JMX Server Insecure Endpoint Code Execution Scanner
Open source ↗Java JMX Server Insecure Configuration Java Code Execution
Open source ↗See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-2342
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.