# CVE-2023-25005: Other in Autodesk InfraWorks

> Attackers can execute arbitrary code via malicious DLLs in Autodesk InfraWorks due to uncontrolled search path elements.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/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:** 12 May 2023
- **Updated:** 27 Jan 2025
- **Also known as:** GHSA-fvwx-63p4-jv5q

## What is CVE-2023-25005?

CVE-2023-25005 is a high-severity vulnerability in Autodesk InfraWorks, published on 12 May 2023. 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

A maliciously crafted DLL file can be forced to read beyond allocated boundaries in Autodesk InfraWorks 2023, and 2021 when parsing the DLL files could lead to a resource injection vulnerability.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2023-25005?

It affects 1 product.


Products: Autodesk Infraworks.

## How do I fix CVE-2023-25005?

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

## Is CVE-2023-25005 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25005 and fix it if it is affected.

What it is: CVE-2023-25005 is a high-severity vulnerability in Autodesk InfraWorks, published on 12 May 2023. 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-2023-25005 in the wild and no public exploit code.

Affected product: Autodesk InfraWorks. 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-2023-25005/ (Markdown: https://insights.sbomify.com/CVE-2023-25005/index.md)
```

## Sources

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

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