# CVE-2016-6645: Code injection in n/a

> Remote authenticated users can execute arbitrary code in EMC Unisphere for VMAX via crafted input to specific request classes.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x7m5-r44w-528r

## What is CVE-2016-6645?

CVE-2016-6645 is a high-severity code injection vulnerability in n/a, published on 5 Oct 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The vApp Managers web application in EMC Unisphere for VMAX Virtual Appliance 8.x before 8.3.0 and Solutions Enabler Virtual Appliance 8.x before 8.3.0 allows remote authenticated users to execute arbitrary code via crafted input to the (1) GeneralCmdRequest, (2) PersistantDataRequest, or (3) GetCommandExecRequest class.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2016-6645?

It affects 3 products.


Products: Dell Emc Unisphere, Emc Solutions Enabler, Emc Unisphere.

## How do I fix CVE-2016-6645?

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

## Is CVE-2016-6645 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-14375](https://insights.sbomify.com/CVE-2017-14375/): Auth bypass in EMC VMAX Virtual Appliance (vApp) EMC Unisphere for VMAX Virtual Appliance versions prior to 8.4.0.15, EMC Solutions Enabler Virtual Appliance versions prior to 8.4.0.15, EMC VASA Virtual Appliance versions prior to 8.4.0.512, EMC VMAX Embedded Management (eManagement) versions prior to and including 1.4 (Enginuity Release 5977.1125.1125 and earlier) (critical 9.8)
- [CVE-2016-6646](https://insights.sbomify.com/CVE-2016-6646/): Code injection in n/a (critical 9.8)
- [CVE-2016-0889](https://insights.sbomify.com/CVE-2016-0889/): Path traversal in n/a (critical 9.8)
- [CVE-2013-3287](https://insights.sbomify.com/CVE-2013-3287/): Information disclosure in n/a (low 1.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6645 and fix it if it is affected.

What it is: CVE-2016-6645 is a high-severity code injection vulnerability in n/a, published on 5 Oct 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6645 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-2016-6645/ (Markdown: https://insights.sbomify.com/CVE-2016-6645/index.md)
```

## Sources

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

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