# CVE-2024-9491: Uncontrolled search path can lead to DLL hijacking in Configuration Wizard 2 installer

> Attackers can execute arbitrary code and escalate privileges via DLL hijacking in the Configuration Wizard 2 installer due to an uncontrolled search path.

- **Severity:** High 8.6 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-mrch-6g3f-vm3c

## What is CVE-2024-9491?

CVE-2024-9491 is a high-severity path traversal vulnerability in silabs.com Configuration Wizard 2, published on 24 Jan 2025. 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

DLL hijacking vulnerabilities, caused by an uncontrolled search path in Configuration Wizard 2 installer can lead to privilege escalation and arbitrary code execution when running the impacted installer.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2024-9491 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9491 is a high-severity path traversal vulnerability in silabs.com Configuration Wizard 2, published on 24 Jan 2025. 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-9491 in the wild and no public exploit code.

Affected product: silabs.com Configuration Wizard 2. 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-9491/ (Markdown: https://insights.sbomify.com/CVE-2024-9491/index.md)
```

## Sources

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

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