CVE-2024-10228: The Vagrant VMWare Utility Windows installer targeted a custom location with a non-protected path that could b

Q: How do I fix CVE-2024-10228?

vagrant vmware utility: upgrade to 1.0.23. Exact commands for each OS are on this page.

Q: Is CVE-2024-10228 being exploited?

CVE-2024-10228 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-10228 affect?

CVE-2024-10228 affects vagrant vmware utility. Severity is low (CVSS 3.8). 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,

Q: How urgent is CVE-2024-10228?

Priority 14/100. No elevated risk signals yet.

Routine

LOW 3.8UPGRADE

CVE-2024-10228 is a low-severity flaw (CVSS 3.8) affecting vagrant vmware utility. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.23

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.8 (Low)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.1% (top 96%)
CISA exploited list	No
Weakness	CWE-732
Published	2024-10-29
Last modified	2026-06-17

Publisher (CNA): HashiCorp Inc. · Vendor: hashicorp

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-10-29 22:15 UTCPublished CVE record published
2026-06-17 06:55 UTCUpdated Record last modified

hashicorp vagrant vmware utility UPGRADE

Affected: < 1.0.23

Fixed in: 1.0.23

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy vagrant-vmware-utility || rpm -q vagrant-vmware-utility || vagrant-vmware-utility --version

2. UPGRADE to 1.0.23 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade vagrant-vmware-utility

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vagrant-vmware-utility

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-10228?

vagrant vmware utility: upgrade to 1.0.23. Exact commands for each OS are on this page.

Is CVE-2024-10228 being exploited?

CVE-2024-10228 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-10228 affect?

CVE-2024-10228 affects vagrant vmware utility. Severity is low (CVSS 3.8). 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,

How urgent is CVE-2024-10228?

Priority 14/100. No elevated risk signals yet.

Software pages

Windows vulnerabilities · VMware vulnerabilities

References

← Back to latest CVEs