# CVE-2016-7457: Privilege escalation in n/a

> Remote authenticated users can gain privileges or halt and remove virtual machines in VMware vRealize Operations.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xm6j-mv8r-9mhp

## What is CVE-2016-7457?

CVE-2016-7457 is a critical vulnerability in n/a, published on 29 Dec 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VMware vRealize Operations (aka vROps) 6.x before 6.4.0 allows remote authenticated users to gain privileges, or halt and remove virtual machines, via unspecified vectors.

Weakness: CWE-264

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

It affects 1 product.


Products: Vmware Vrealize Operations.

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

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

## Is CVE-2016-7457 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-3943](https://insights.sbomify.com/CVE-2020-3943/): Code injection in vRealize Operations for Horizon Adapter (critical 9.8)
- [CVE-2023-20856](https://insights.sbomify.com/CVE-2023-20856/): Cross-site request forgery in VMware vRealize Operations (vROps) (high 8.8)
- [CVE-2022-31673](https://insights.sbomify.com/CVE-2022-31673/): Information disclosure in VMware vRealize Operations (high 8.8)
- [CVE-2020-3944](https://insights.sbomify.com/CVE-2020-3944/): Auth bypass in vRealize Operations for Horizon Adapter (high 8.6)
- [CVE-2016-7462](https://insights.sbomify.com/CVE-2016-7462/): Deserialization in n/a (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-7457 is a critical vulnerability in n/a, published on 29 Dec 2016. 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-2016-7457 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-7457/ (Markdown: https://insights.sbomify.com/CVE-2016-7457/index.md)
```

## Sources

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

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