CVE-2017-16839
First published: Thu Mar 29 2018(Updated: )
Hashicorp vagrant-vmware-fusion 5.0.4 allows local users to steal root privileges if VMware Fusion is not installed.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| HashiCorp Vagrant | =5.0.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-16839?
CVE-2017-16839 is considered to have high severity due to its potential for privilege escalation.
How do I fix CVE-2017-16839?
To fix CVE-2017-16839, ensure that VMware Fusion is installed and properly configured on your system.
Who is affected by CVE-2017-16839?
Local users on systems running Hashicorp Vagrant VMware Fusion version 5.0.4 without VMware Fusion installed are affected by CVE-2017-16839.
Can CVE-2017-16839 allow remote exploitation?
No, CVE-2017-16839 is not a remote exploitation vulnerability; it requires local access to the affected system.
What types of systems are vulnerable to CVE-2017-16839?
Systems using Hashicorp Vagrant VMware Fusion version 5.0.4 without VMware Fusion installed are vulnerable to CVE-2017-16839.
- agent/severity
- agent/references
- agent/author
- agent/description
- agent/type
- agent/event
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/hashicorp
- canonical/hashicorp vagrant
- version/hashicorp vagrant/5.0.4