dbcve.org
Advance SteelApplication · Autodesk

CVE-2022-25790

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 file in Autodesk AutoCAD 2022, 2021, 2020, 2019 and Autodesk Navisworks 2022 can be used to write beyond the allocated boundaries when parsing the DWF files. 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 · moderate confidence

A buffer overflow vulnerability exists in the DWF file parsing component of AutoCAD and Navisworks. When parsing a specially crafted DWF file, the software writes data beyond allocated memory boundaries due to insufficient bounds checking, potentially allowing arbitrary code execution.

MitigationApply vendor-supplied security patches for all affected AutoCAD and Navisworks versions. Until patched, exercise caution when opening DWF files from untrusted or 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 AutoCAD product variant
    Open the application and check Help > About or the product splash screen to confirm the specific product name (e.g., AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, or Advance Steel)
    Affected if The product is any of the listed affected Autodesk products
  2. Check installed product version
    In the application, go to Help > About or check the program information dialog to view the full version number (e.g., 2020.1.3)
    Affected if The version falls within any of these 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 file handling capability
    Confirm the installed product can open or process DWF files, which is a native capability of AutoCAD-based products; check if the DWG TrueView utility or any DWF-related tools are present
    Affected if The product includes DWF file reading or writing functionality, which is standard in these AutoCAD variants

If the installed product is any Autodesk AutoCAD variant (or Advance Steel) with a version number matching the affected ranges and DWF file handling is enabled, the environment is vulnerable to this buffer overflow.

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-supplied security patches for all affected AutoCAD and Navisworks versions. Until patched, exercise caution when opening DWF files from untrusted or unknown sources.

Recommended fix High confidence

Upgrade to the minimum fixed version for your product line: 2019.1.4, 2020.1.5, 2021.1.2, or 2022.1.2 (or later)

  1. Identify the currently installed Autodesk product version (Advance Steel, AutoCAD, or variant) from the Help > About menu
  2. Determine which affected version line the installation belongs to (2019, 2020, 2021, or 2022)
  3. Download the corresponding fixed version from the Autodesk website or your Autodesk Account portal: 2019.1.4 or later for 2019.x line, 2020.1.5 or later for 2020.x line, 2021.1.2 or later for 2021.x line, 2022.1.2 or later for 2022.x line
  4. Install the update following standard Autodesk update procedures
  5. Verify the update was successful by checking Help > About to confirm the installed version matches the fixed release
  6. Restart the application after applying the update
Caveat Standard Autodesk update considerations apply - review release notes for your specific version for any changes to functionality or system requirements

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
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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