CVE-2017-16512: Race Condition
First published: Thu Mar 29 2018(Updated: )
The vagrant update process in Hashicorp vagrant-vmware-fusion 5.0.2 through 5.0.4 allows local users to steal root privileges via a crafted update request when no updates are available.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| HashiCorp Vagrant | >=5.0.2<=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-16512?
CVE-2017-16512 has a medium severity score due to its potential to allow local users to escalate privileges.
How do I fix CVE-2017-16512?
To fix CVE-2017-16512, update HashiCorp Vagrant VMware Fusion to version 5.0.5 or later.
Who is affected by CVE-2017-16512?
Local users running HashiCorp Vagrant VMware Fusion versions 5.0.2 through 5.0.4 are affected by CVE-2017-16512.
What are the risks associated with CVE-2017-16512?
The risks associated with CVE-2017-16512 include local privilege escalation which could lead to unauthorized access to system resources.
How was CVE-2017-16512 discovered?
CVE-2017-16512 was discovered during a review of the vagrant update process, revealing vulnerabilities in handling update requests.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/weakness
- agent/severity
- agent/last-modified-date
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/hashicorp
- canonical/hashicorp vagrant
- version/hashicorp vagrant/5.0.2
- version/hashicorp vagrant/5.0.4