# CVE-2015-6934: Deserialization in n/a

> Remote attackers can execute arbitrary commands via crafted serialized Java objects in VMware vRealize Orchestrator and related products.

- **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-24pf-jwjh-vhjw

## What is CVE-2015-6934?

CVE-2015-6934 is a high-severity unsafe deserialization vulnerability in n/a, published on 21 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Serialized-object interfaces in VMware vRealize Orchestrator 6.x, vCenter Orchestrator 5.x, vRealize Operations 6.x, vCenter Operations 5.x, and vCenter Application Discovery Manager (vADM) 7.x allow remote attackers to execute arbitrary commands via a crafted serialized Java object, related to the Apache Commons Collections library.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Vmware Vcenter Orchestrator, Vmware Vrealize Orchestrator.

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

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

## Is CVE-2015-6934 being exploited?

There is no known exploitation of CVE-2015-6934 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2012-1513](https://insights.sbomify.com/CVE-2012-1513/): Information disclosure in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-6934 is a high-severity unsafe deserialization vulnerability in n/a, published on 21 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6934 in the wild and no public exploit code.

Affected product: n/a. 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-6934/ (Markdown: https://insights.sbomify.com/CVE-2015-6934/index.md)
```

## Sources

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

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