dbcve.org
InfraworksApplication · Autodesk

CVE-2023-25005

HIGH · 7.8 CVSS v3.1 Published 2023-05-12
Fix available
A fix is available. Upgrade to 2021.2 / 2023.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an out-of-bounds read vulnerability in Autodesk InfraWorks 2021 and 2023 where parsing maliciously crafted DLL files allows reading beyond allocated memory boundaries, leading to a resource injection vulnerability where attackers can inject malicious resources through the DLL loading mechanism.

MitigationApply the official Autodesk security patches for InfraWorks 2021 and 2023 when available. Until then, avoid opening untrusted DLL files from unknown sources and implement network segmentation to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
InfraworksApplication
Affected:>= 2021.0, < 2021.2>= 2023.0, < 2023.1= 2021.2= 2023.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm InfraWorks installation
    Check for Autodesk InfraWorks in the program files directory (typically C:\Program Files\Autodesk\InfraWorks) or via Add/Remove Programs in Control Panel
    Affected if InfraWorks is installed on the system
  2. Identify installed InfraWorks version
    Right-click the InfraWorks executable in the installation folder, select Properties, then go to the Details tab to view the File Version. Alternatively, open InfraWorks and go to Help > About Autodesk InfraWorks to see the version number
    Affected if The displayed version is any release from 2021.0 through 2023.1 (including 2021.0, 2021.1, 2021.2, 2023.0, and 2023.1)
  3. Verify DLL file handling exposure
    Search the system for any recently added or suspicious DLL files in InfraWorks working directories, network shares, or download folders associated with InfraWorks projects
    Affected if Untrusted or unfamiliar DLL files are present in locations where InfraWorks loads or references DLLs

The environment is affected if Autodesk InfraWorks versions 2021.0 through 2023.1 are installed and the user opens or processes untrusted DLL files within that software.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2021.2 / 2023.1 or later
Fixed in 2021.22023.1
Interim mitigation

Apply the official Autodesk security patches for InfraWorks 2021 and 2023 when available. Until then, avoid opening untrusted DLL files from unknown sources and implement network segmentation to limit exposure.

Recommended fix High confidence

InfraWorks 2021.2 or later; InfraWorks 2023.1 or later

  1. 1. Identify the currently installed Autodesk InfraWorks version from the Help > About menu
  2. 2. Download Autodesk InfraWorks 2021.2 or later (for 2021.x line) or version 2023.1 or later (for 2023.x line) from the official Autodesk website (www.autodesk.com)
  3. 3. Close all Autodesk applications and any running processes related to InfraWorks
  4. 4. Run the installer with administrator privileges
  5. 5. Follow the on-screen installation prompts to complete the upgrade
  6. 6. Restart the system after installation completes
  7. 7. Verify the installed version matches the fixed release (2021.2 or 2023.1 and above)
Caveat Review Autodesk's release notes for any feature changes between your current version and the target fixed version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Infraworks Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25005 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25005 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data