# CVE-2017-16873: Privilege escalation in n/a

> Attackers can exploit an unsanitized PATH in the suid binary to escalate privileges to root on systems using the Vagrant VMware Fusion plugin.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v2px-fp32-982g

## What is CVE-2017-16873?

CVE-2017-16873 is a high-severity vulnerability in n/a, published on 29 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

It is possible to exploit an unsanitized PATH in the suid binary that ships with vagrant-vmware-fusion 4.0.25 through 5.0.4 in order to escalate to root privileges.

## Which versions are affected by CVE-2017-16873?

It affects 1 product.


Products: Hashicorp Vagrant Vmware Fusion.

## How do I fix CVE-2017-16873?

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

## Is CVE-2017-16873 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11741](https://insights.sbomify.com/CVE-2017-11741/): Privilege escalation in n/a (high 8.8)
- [CVE-2017-16512](https://insights.sbomify.com/CVE-2017-16512/): Race condition in n/a (high 7.8)
- [CVE-2017-12579](https://insights.sbomify.com/CVE-2017-12579/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-7642](https://insights.sbomify.com/CVE-2017-7642/): Privilege escalation in n/a (high 7.8)
- [CVE-2017-16839](https://insights.sbomify.com/CVE-2017-16839/): Privilege escalation in n/a (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16873 and fix it if it is affected.

What it is: CVE-2017-16873 is a high-severity vulnerability in n/a, published on 29 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-16873 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-2017-16873/ (Markdown: https://insights.sbomify.com/CVE-2017-16873/index.md)
```

## Sources

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

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