Hashicorp vagrant-vmware-fusion up to 5.0.2 Vagrant Update Process access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Hashicorp vagrant-vmware-fusion up to 5.0.2. This issue affects some unknown processing of the component Vagrant Update Process. The manipulation results in access control. This vulnerability was named CVE-2017-16512. The attack needs to be approached locally. There is no available exploit.
Details
A vulnerability classified as critical has been found in Hashicorp vagrant-vmware-fusion up to 5.0.2. Affected is an unknown code block of the component Vagrant Update Process. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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.
The bug was discovered 03/28/2018. The weakness was presented 03/29/2018 (Website). The advisory is available at m4.rkw.io. This vulnerability is traded as CVE-2017-16512 since 11/03/2017. Local access is required to approach this attack. The requirement for exploitation is a authentication. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-115220 and VDB-115219 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.8
VulDB Base Score: 7.8
VulDB Temp Score: 7.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/03/2017 🔍03/28/2018 🔍
03/29/2018 🔍
03/29/2018 🔍
03/30/2018 🔍
01/18/2020 🔍
Sources
Advisory: m4.rkw.ioStatus: Not defined
CVE: CVE-2017-16512 (🔍)
GCVE (CVE): GCVE-0-2017-16512
GCVE (VulDB): GCVE-100-115218
See also: 🔍
Entry
Created: 03/30/2018 12:24Updated: 01/18/2020 08:32
Changes: 03/30/2018 12:24 (58), 01/18/2020 08:32 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.