dbcve.org
AutocadApplication · Autodesk

CVE-2022-33888

HIGH · 7.8 CVSS v3.1 Published 2022-10-03
Fix available
A fix is available. Upgrade to 2022.1.3 / 2023.1.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 malicious crafted Dwg2Spd file when processed through Autodesk DWG application could lead to memory corruption vulnerability by write access violation. This vulnerability in conjunction with other vulnerabilities could lead to code execution in the context of the current process.

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 memory corruption vulnerability exists in Autodesk DWG applications where processing a maliciously crafted Dwg2Spd file leads to write access violation. This out-of-bounds write can potentially be chained with other vulnerabilities to achieve code execution in the context of the current process. The attack requires user interaction to open the malicious file.

MitigationApply the vendor-supplied patch from Autodesk. Until patched, avoid opening Dwg2Spd files from untrusted sources and consider running the application in an isolated sandbox or virtualized environment to limit potential impact.

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
AutocadApplication
Affected:>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad Advance SteelApplication
Affected:>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad ArchitectureApplication
Affected:>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad Civil 3dApplication
Affected:>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad ElectricalApplication
Affected:>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad LtApplication
Affected:>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad Map 3dApplication
Affected:>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad MechanicalApplication
Affected:>= 2022, < 2022.1.3>= 2023, < 2023.1.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. Identify the installed Autodesk product
    Check the installed programs list in Windows Control Panel or use 'Get-ItemProperty' in PowerShell for registry key 'HKLM:\SOFTWARE\Autodesk\AutoCAD' to determine which AutoCAD variant is installed (e.g., AutoCAD, AutoCAD Architecture, AutoCAD Civil 3D, etc.)
    Affected if Any of the following products are installed: AutoCAD, AutoCAD Advance Steel, AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, or AutoCAD Mechanical
  2. Determine the installed version number
    Run the application and go to Help > About AutoCAD, or check the Windows registry at 'HKLM\SOFTWARE\Autodesk\AutoCAD\<version>' for the 'Version' value, or check the executable properties of the main acad.exe file
    Affected if The version cannot be determined or does not match the expected version format for 2022 or 2023 product lines
  3. Compare the installed version against affected ranges
    If installed version starts with 2022.x, verify if it is less than 2022.1.3. If installed version starts with 2023.x, verify if it is less than 2023.1.1. Use version comparison (e.g., in PowerShell: [version]'2022.1.2' -lt [version]'2022.1.3')
    Affected if The installed version is 2022.x where x < 1.3, OR the installed version is 2023.x where x < 1.1 (e.g., 2022.1.2, 2023.1.0 are vulnerable)
  4. Confirm Dwg2Spd feature is available
    The Dwg2Spd (DWG to Specification) converter is a built-in feature in affected AutoCAD products. Check if the application has the 'Export to Specification' or 'Dwg2Spd' functionality present, typically found under the Export menu or as a plug-in
    Affected if The Dwg2Spd feature exists in the installed product and the version is within the vulnerable range

The environment is affected if any Autodesk AutoCAD variant (or related product) is installed with version 2022.x < 2022.1.3 or version 2023.x < 2023.1.1, as these versions contain the vulnerable Dwg2Spd processing code.

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 2022.1.3 / 2023.1.1 or later
Fixed in 2022.1.32023.1.1
Interim mitigation

Apply the vendor-supplied patch from Autodesk. Until patched, avoid opening Dwg2Spd files from untrusted sources and consider running the application in an isolated sandbox or virtualized environment to limit potential impact.

Recommended fix High confidence

Upgrade to AutoCAD 2022.1.3 or later, or AutoCAD 2023.1.1 or later (and corresponding versions for AutoCAD Architecture, Civil 3D, Electrical, LT, Map 3D, Mechanical, and Advance Steel)

  1. Identify the current installed version of the affected Autodesk product (AutoCAD or its specialized variants)
  2. Navigate to the official Autodesk support website or use the built-in Autodesk Access application to check for updates
  3. Download Autodesk version 2022.1.3 or later for 2022-based installations, or version 2023.1.1 or later for 2023-based installations
  4. Apply the update by running the downloaded installer or using the Autodesk desktop app to install the security update
  5. Restart the application after the update is applied
  6. Verify the installed version matches or exceeds the fixed release (2022.1.3 or 2023.1.1)

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
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,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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