CVE-2017-16873
First published: Thu Mar 29 2018(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| HashiCorp Vagrant | >=4.0.25<=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-16873?
CVE-2017-16873 is classified as a high severity vulnerability due to its potential for privilege escalation.
How do I fix CVE-2017-16873?
To mitigate CVE-2017-16873, update Vagrant VMware Fusion to version 5.0.5 or later.
What are the potential impacts of CVE-2017-16873?
The exploitation of CVE-2017-16873 could allow attackers to achieve root access on affected systems.
Which software versions are affected by CVE-2017-16873?
CVE-2017-16873 affects Vagrant VMware Fusion versions 4.0.25 through 5.0.4.
Is CVE-2017-16873 specific to certain operating systems?
CVE-2017-16873 is primarily relevant to systems using the vulnerable versions of Vagrant VMware Fusion.
- agent/severity
- agent/references
- agent/author
- agent/event
- agent/type
- agent/description
- agent/first-publish-date
- agent/softwarecombine
- agent/last-modified-date
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/hashicorp
- canonical/hashicorp vagrant
- version/hashicorp vagrant/4.0.25
- version/hashicorp vagrant/5.0.4