dbcve.org
Advance SteelApplication · Autodesk

CVE-2022-25791

HIGH · 7.8 CVSS v3.1 Published 2022-04-11
Fix available
A fix is available. Upgrade to 2019.1.4 / 2020.1.5 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 Memory Corruption vulnerability for DWF and DWFX files in Autodesk AutoCAD 2022, 2021, 2020, 2019 and Autodesk Navisworks 2022 may lead to code execution through maliciously crafted DLL files.

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 · high confidence

Memory corruption vulnerability in the DWF and DWFX file parsing components of Autodesk AutoCAD and Navisworks allows code execution via maliciously crafted files that leverage malicious DLL files during the parsing process.

MitigationApply the vendor security updates released by Autodesk for the affected versions (2019-2022) of AutoCAD and Navisworks to address the memory corruption and DLL loading vulnerability in file parsers.

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
Advance SteelApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2
AutocadApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2>= 2022, < 2022.2.2
Autocad ArchitectureApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2
Autocad ElectricalApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2
Autocad LtApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2
Autocad Map 3dApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2
Autocad MechanicalApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2
Autocad MepApplication
Affected:>= 2019, < 2019.1.4>= 2020, < 2020.1.5>= 2021, < 2021.1.2>= 2022, < 2022.1.2

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. Identify installed Autodesk products
    Open Windows Control Panel > Programs and Features, or check C:\Program Files\Autodesk for installed product folders. Look for AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, Advance Steel, or Navisworks.
    Affected if Any of these products are present on the system
  2. Determine the installed version number
    Right-click the product executable (e.g., acad.exe for AutoCAD) in its installation folder, select Properties, then view the Details tab for the Product version. Alternatively, launch the application and go to Help > About [Product Name].
    Affected if The version falls within these affected ranges: 2019.x (before 2019.1.4), 2020.x (before 2020.1.5), 2021.x (before 2021.1.2), or 2022.x (before 2022.1.2, or before 2022.2.2 for vanilla AutoCAD)
  3. Verify DWF/DWFX file handling is enabled
    Check if the product has DWF and DWFX file format support modules loaded. In AutoCAD, run the (.about) command or check the installed plug-ins. These file formats are typically supported out-of-the-box in affected versions.
    Affected if The product includes DWF or DWFX file parsing capability, which is standard in AutoCAD and Navisworks installations
  4. Review recent DWF/DWFX file activity
    Check the application recent files list or Windows Prefetch for evidence of DWF or DWFX file opening. These file extensions indicate the parsing component may have been invoked.
    Affected if DWF or DWFX files have been opened recently using the installed product, confirming the vulnerable code path was exercised

The environment is affected if any of the listed Autodesk products (AutoCAD variants, Advance Steel, Navisworks) are installed with version 2019, 2020, 2021, or 2022 that falls below 2019.1.4, 2020.1.5, 2021.1.2, or 2022.1.2 respectively.

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 2019.1.4 / 2020.1.5 / 2021.1.2 or later
Fixed in 2019.1.42020.1.52021.1.2
Interim mitigation

Apply the vendor security updates released by Autodesk for the affected versions (2019-2022) of AutoCAD and Navisworks to address the memory corruption and DLL loading vulnerability in file parsers.

Recommended fix High confidence

Upgrade to 2019.1.4 (or later), 2020.1.5 (or later), 2021.1.2 (or later), or 2022.1.2 (or later) depending on your release year

  1. Identify your current AutoCAD or Advance Steel version by clicking the Help menu and selecting About Autodesk [Product Name]
  2. Note the release year (2019, 2020, 2021, or 2022)
  3. Download and install the appropriate update: For 2019.x, install update 2019.1.4 or later; For 2020.x, install update 2020.1.5 or later; For 2021.x, install update 2021.1.2 or later; For 2022.x, install update 2022.1.2 or later
  4. Verify the update was successful by checking the version again in the About dialog
  5. Restart the application after applying the update
Caveat Standard Autodesk update—backup custom files and settings before upgrading; some older custom scripts or plugins may require revalidation

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

Fix this in Advance Steel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25791 — 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-2022-25791 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