dbcve.org
Advance SteelApplication · Autodesk

CVE-2022-25792

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 DXF file in Autodesk AutoCAD 2022, 2021, 2020, 2019 and Autodesk Navisworks 2022 can be used to write beyond the allocated buffer through Buffer overflow vulnerability. This vulnerability can be exploited to execute arbitrary code.

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 buffer overflow vulnerability exists in Autodesk AutoCAD and Navisworks when parsing maliciously crafted DXF files. The vulnerability allows writing beyond the allocated buffer boundary during DXF file processing, which can be exploited to achieve arbitrary code execution.

MitigationApply the vendor-supplied security update for affected AutoCAD and Navisworks versions. Until patched, avoid opening DXF 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 Autodesk product
    Open Windows Settings > Apps & Features or check Programs and Features in Control Panel. Look for Autodesk AutoCAD, Autodesk Advance Steel, or any Autodesk AutoCAD-based product (Architecture, Electrical, LT, Map 3D, Mechanical, MEP).
    Affected if Any of the affected products (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, or Advance Steel) are installed.
  2. Determine the product version
    For AutoCAD products, the version is typically visible in the Programs and Features list, or you can open the application and go to Help > About Autodesk [Product]. The version number follows the format YYYY.x (e.g., 2022.1.2).
    Affected if The version shown matches one of the affected version ranges: 2019.x where x < 1.4; 2020.x where x < 1.5; 2021.x where x < 1.2; or 2022.x where x < 1.2 (or < 2.2 for plain AutoCAD 2022).
  3. Confirm DXF file handling is enabled
    DXF is a native AutoCAD file format. By default, AutoCAD and its vertical products (Architecture, Electrical, Mechanical, etc.) can open and parse DXF files. Check if the application is configured to handle DXF files by default or if DXF file association exists on the system.
    Affected if The installed product can open or import DXF files, which is the default behavior for affected AutoCAD-based products.
  4. Check if untrusted DXF files can be processed
    Review whether the system has user access controls that would prevent a user from opening a malicious DXF file. Verify file handling permissions and whether email or download folders are accessible to the AutoCAD process.
    Affected if Users can open DXF files from external or untrusted sources within the AutoCAD environment.

You are affected if you have any of the listed Autodesk products installed and the version falls within the vulnerable ranges (2019.x before 1.4, 2020.x before 1.5, 2021.x before 1.2, or 2022.x before 1.2 or 2.2 depending on product), and the product can process DXF files.

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-supplied security update for affected AutoCAD and Navisworks versions. Until patched, avoid opening DXF files from untrusted or unknown sources.

Recommended fix High confidence

Upgrade to version 2019.1.4 or later for AutoCAD 2019; 2020.1.5 or later for 2020; 2021.1.2 or later for 2021; 2022.1.2 or later for 2022

  1. Open Autodesk AutoCAD or the specific affected product
  2. Navigate to the Help menu and select 'Check for Updates' or use the Autodesk Access app
  3. Alternatively, download the update from the Autodesk Account portal: account.autodesk.com
  4. For each affected version (2019, 2020, 2021, 2022), apply the corresponding update: 2019.1.4, 2020.1.5, 2021.1.2, or 2022.1.2
  5. Restart the application after applying the update
  6. Verify the version by typing 'ABOUT' in the command line to confirm the update was successful
Caveat Standard Autodesk update—back up custom scripts, profiles, and customizations before applying

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

Fix this in Advance Steel Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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