# CVE-2024-10228: Vagrant VMWare Utility installation files vulnerable to modification by unprivileged user

> Unprivileged users can modify installer files in a non-protected path, potentially leading to privilege escalation or code execution during installation.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2024
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-f8cq-cpqj-phg9

## What is CVE-2024-10228?

CVE-2024-10228 is a low-severity vulnerability in HashiCorp Vagrant, published on 29 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2024-10228?

It affects 1 product.


Products: Hashicorp Vagrant Vmware Utility.

## How do I fix CVE-2024-10228?

No fix has been published for CVE-2024-10228 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-10228 being exploited?

There is no known exploitation of CVE-2024-10228 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10228 and fix it if it is affected.

What it is: CVE-2024-10228 is a low-severity vulnerability in HashiCorp Vagrant, published on 29 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10228 in the wild and no public exploit code.

Affected product: HashiCorp Vagrant. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-10228/ (Markdown: https://insights.sbomify.com/CVE-2024-10228/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10228
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10228
- OSV: https://osv.dev/vulnerability/CVE-2024-10228

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-10228/
Summaries are generated and may contain mistakes; the official description above is the record.