# CVE-2024-29188: Malicious directory junction can cause WiX RemoveFoldersEx to possibly delete elevated files

> Attackers can delete protected system files via directory junctions in WiX installers, requiring admin approval for execution.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Mar 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-jx4p-m4wm-vvjg

## What is CVE-2024-29188?

CVE-2024-29188 is a high-severity path traversal vulnerability in wixtoolset issues, published on 24 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

WiX toolset lets developers create installers for Windows Installer, the Windows installation engine. The custom action behind WiX's `RemoveFolderEx` functionality could allow a standard user to delete protected directories. `RemoveFolderEx` deletes an entire directory tree during installation or uninstallation. It does so by recursing every subdirectory starting at a specified directory and adding each subdirectory to the list of directories Windows Installer should delete. If the setup author instructed `RemoveFolderEx` to delete a per-user folder from a per-machine installer, an attacker could create a directory junction in that per-user folder pointing to a per-machine, protected directory. Windows Installer, when executing the per-machine installer after approval by an administrator, would delete the target of the directory junction. This vulnerability is fixed in 3.14.1 and 4.0.5.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

6 open source packages ship an affected version, including WixToolset.Util.wixext and wix.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `WixToolset.Util.wixext` | NuGet | All versions | 4.0.5 |
| `WixToolset.Util.wixext` | NuGet | All versions | 4.0.5 |
| `wix` | NuGet | All versions | 3.14.1 |
| `wix` | NuGet | All versions | 3.14.1 |
| `wix` | NuGet | From 4.0.0 | 4.0.5 |
| `wix` | NuGet | From 4.0.0 | 4.0.5 |

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

Upgrade WixToolset.Util.wixext to 4.0.5 or later.

## Is CVE-2024-29188 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29188 is a high-severity path traversal vulnerability in wixtoolset issues, published on 24 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-29188 in the wild and no public exploit code.

Affected packages and fixed versions:
- WixToolset.Util.wixext (NuGet): affected all versions; fixed in 4.0.5
- WixToolset.Util.wixext (NuGet): affected all versions; fixed in 4.0.5
- wix (NuGet): affected all versions; fixed in 3.14.1
- wix (NuGet): affected all versions; fixed in 3.14.1
- wix (NuGet): affected from 4.0.0; fixed in 4.0.5
- wix (NuGet): affected from 4.0.0; fixed in 4.0.5

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-29188/ (Markdown: https://insights.sbomify.com/CVE-2024-29188/index.md)
```

## Sources

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

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