The Vagrant VMWare Utility Windows installer targeted a custom location with a non-protected path that could be modified by an unprivileged user, introducing potential for unauthorized file system writes. This vulnerability, CVE-2024-10228, was fixed in Vagrant VMWare Utility 1.0...
Product
hashicorp github.com/hashicorp/vagrant vulnerabilities
5 published CVES affecting hashicorp github.com/hashicorp/vagrant, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 0
- High
- 4
- Medium
- 0
- Low
- 1
- Unscored
- 0
- CISA KEV
- 0
Latest hashicorp github.com/hashicorp/vagrant CVEs
Newest publication first
-
LowCVSS 3.3 EPSS 0.14%
-
HighCVSS 7.8 EPSS 0.24%
HashiCorp Vagrant's Windows installer targeted a custom location with a non-protected path that could be junctioned, introducing potential for unauthorized file system writes. Fixed in Vagrant 2.4.0.
-
HighCVSS 7.8 EPSS 0.25%
An issue was discovered in Hashicorp Packer before 2.3.1. The recommended sudoers configuration for Vagrant on Linux is insecure. If the host has been configured according to this documentation, non-privileged users on the host can leverage a wildcard in the sudoers configuration...
-
HighCVSS 7.8 EPSS 0.98% Public exploit
If HashiCorp Vagrant VMware Fusion plugin (aka vagrant-vmware-fusion) 5.0.3 is installed but VMware Fusion is not, a local attacker can create a fake application directory and exploit the suid sudo helper in order to escalate to root.
-
HighCVSS 7.8 EPSS 0.93% Public exploit
In HashiCorp Vagrant VMware Fusion plugin (aka vagrant-vmware-fusion) 5.0.1, a local attacker or malware can silently subvert the plugin update process in order to escalate to root privileges.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.