# CVE-2015-2342: Code injection in n/a

> Remote attackers can execute arbitrary code on VMware vCenter Server via the JMX RMI service due to unrestricted MBean registration.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w37r-rg6f-g7rh

## What is CVE-2015-2342?

CVE-2015-2342 is a critical code injection vulnerability in Vmware Vcenter Server, published on 12 Oct 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2015-2342?

It affects 1 product.


Products: Vmware Vcenter Server.

## How do I fix CVE-2015-2342?

No fix has been published for CVE-2015-2342 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-2342 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-2342 exists.

Public exploit code:

- Java JMX Server Insecure Endpoint Code Execution Scanner (metasploit)
- Java JMX Server Insecure Configuration Java Code Execution (metasploit)
- Java JMX - Server Insecure Configuration Java Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in Vmware Vcenter Server

- [CVE-2026-59310](https://insights.sbomify.com/CVE-2026-59310/): Broadcom VMware vCenter Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2023-34048](https://insights.sbomify.com/CVE-2023-34048/): VMware vCenter Server Out-of-Bounds Write (critical 9.8, exploited in the wild)
- [CVE-2020-3952](https://insights.sbomify.com/CVE-2020-3952/): VMware vCenter Server Information Disclosure (critical 9.8, exploited in the wild)
- [CVE-2021-22017](https://insights.sbomify.com/CVE-2021-22017/): VMware vCenter Server Improper Access Control (medium 5.3, exploited in the wild)
- [CVE-2026-59309](https://insights.sbomify.com/CVE-2026-59309/): vCenter authentication-bypass vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2342 and fix it if it is affected.

What it is: CVE-2015-2342 is a critical code injection vulnerability in Vmware Vcenter Server, published on 12 Oct 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-2342 exists.

Affected product: Vmware Vcenter Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-2342/ (Markdown: https://insights.sbomify.com/CVE-2015-2342/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-2342
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-2342
- OSV: https://osv.dev/vulnerability/CVE-2015-2342

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-2342/
Summaries are generated and may contain mistakes; the official description above is the record.