CVE-2017-16839 Privilege escalation in n/a
High 7.0
Published
Updated
Check this codebase for CVE-2017-16839 and fix it if it is affected.
What it is: CVE-2017-16839 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-16839 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-16839/ (Markdown: https://insights.sbomify.com/CVE-2017-16839/index.md)
Local attackers can gain root privileges via the Vagrant VMware Fusion plugin when VMware Fusion is not installed.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2017-16839?
CVE-2017-16839 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
Hashicorp vagrant-vmware-fusion 5.0.4 allows local users to steal root privileges if VMware Fusion is not installed.
Which versions are affected by CVE-2017-16839?
It affects 1 product.
Products include Hashicorp Vagrant Vmware Fusion.
How do I fix CVE-2017-16839?
No fix has been published for CVE-2017-16839 yet. Limit exposure of the affected software until one is available.
Is CVE-2017-16839 being exploited?
There is no known exploitation of CVE-2017-16839 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-vp7x-mh2p-w87q.