dbcve.org
Advance SteelApplication · Autodesk

CVE-2022-25789

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 maliciously crafted DWF, 3DS and DWFX files in Autodesk AutoCAD 2022, 2021, 2020, 2019 can be used to trigger use-after-free vulnerability. Exploitation of this vulnerability may lead to code execution.

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

A use-after-free vulnerability exists in Autodesk AutoCAD 2019-2022 when parsing maliciously crafted DWF, 3DS, and DWFX files. The vulnerability occurs when memory is freed but still referenced, allowing an attacker to manipulate memory and achieve code execution.

MitigationApply vendor patches when available. Until then, restrict opening untrusted DWF/3DS/DWFX files and educate users about opening files from unknown sources.

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 product
    Check Windows registry under HKLM\SOFTWARE\Autodesk\AutoCAD or look in Add/Remove Programs for Autodesk product names such as AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, or Advance Steel
    Affected if Any of these Autodesk products are installed
  2. Determine installed version and build number
    Open AutoCAD and type VER or ABOUT at the command prompt, or check registry key HKLM\SOFTWARE\Autodesk\AutoCAD\<version>\Setup\InstallPath for the installed version string
    Affected if Version matches the 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 plain AutoCAD)
  3. Verify DWF/DWFX/3DS import capability
    Check if the application has the standard file open dialog and verify that DWF, 3DS, and DWFX extensions are listed as supported import formats in the application options or by attempting to open a sample file
    Affected if The application can import or open DWF, 3DS, or DWFX files, making the parsing code reachable

The environment is affected if any Autodesk product from the list is installed with a version falling between 2019 and the fixed releases (2019.1.4, 2020.1.5, 2021.1.2, or 2022.1.2/2022.2.2 depending on product and year), and the application supports parsing DWF/3DS/DWFX file formats.

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 vendor patches when available. Until then, restrict opening untrusted DWF/3DS/DWFX files and educate users about opening files from unknown sources.

Recommended fix High confidence

Upgrade to the latest version within your product year: 2019.1.4+, 2020.1.5+, 2021.1.2+, or 2022.1.2+ depending on your baseline release

  1. 1. Identify the exact installed version of your Autodesk product (Advance Steel, AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, or AutoCAD MEP) from the Help > About menu.
  2. 2. Close any running instances of the Autodesk application.
  3. 3. If your version is 2019.x and less than 2019.1.4, upgrade to version 2019.1.4 or later.
  4. 4. If your version is 2020.x and less than 2020.1.5, upgrade to version 2020.1.5 or later.
  5. 5. If your version is 2021.x and less than 2021.1.2, upgrade to version 2021.1.2 or later.
  6. 6. If your version is 2022.x and less than 2022.1.2, upgrade to version 2022.1.2 or later.
  7. 7. Download the appropriate update from the Autodesk Account portal or the official Autodesk support website (www.autodesk.com).
  8. 8. Install the update following the on-screen instructions.
Caveat Standard Autodesk update; test custom scripts/libraries after upgrading to ensure compatibility

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

Fix this in Advance Steel Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
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,760.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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