dbcve.org
AutocadApplication · Autodesk

CVE-2022-33884

HIGH · 7.5 CVSS v3.1 Published 2022-10-03
Fix available
A fix is available. Upgrade to 2020.1.6 / 2021.1.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Parsing a maliciously crafted X_B file can force Autodesk AutoCAD 2023 and 2022 to read beyond allocated boundaries. 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

This is an out-of-bounds read vulnerability in Autodesk AutoCAD 2022 and 2023 where parsing a maliciously crafted X_B file causes the application to read beyond allocated memory boundaries. While the vulnerability alone leads to a read condition, it can be chained with other vulnerabilities to achieve arbitrary code execution in the context of the current process.

MitigationApply vendor patches from Autodesk for AutoCAD 2022 and 2023. Until patched, exercise caution when opening X_B files from untrusted sources, as malformed files can trigger the out-of-bounds read.

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:>= 2020, < 2020.1.6>= 2021, < 2021.1.3>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad Advance SteelApplication
Affected:>= 2020, < 2020.1.6>= 2021, < 2021.1.3>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad ArchitectureApplication
Affected:>= 2020, < 2020.1.6>= 2021, < 2021.1.3>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad Civil 3dApplication
Affected:>= 2020, < 2020.1.6>= 2021, < 2021.1.3>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad ElectricalApplication
Affected:>= 2020, < 2020.1.6>= 2021, < 2021.1.3>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad LtApplication
Affected:>= 2020, < 2020.1.6>= 2021, < 2021.1.3>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad Map 3dApplication
Affected:>= 2020, < 2020.1.6>= 2021, < 2021.1.3>= 2022, < 2022.1.3>= 2023, < 2023.1.1
Autocad MechanicalApplication
Affected:>= 2020, < 2020.1.6>= 2021, < 2021.1.3>= 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 AutoCAD product variant
    Open AutoCAD and go to Help > About Autodesk AutoCAD, or run the application and check the title bar/splash screen for the product name (e.g., AutoCAD, AutoCAD Architecture, AutoCAD Civil 3D, etc.)
    Affected if The product is one of: AutoCAD, AutoCAD Advance Steel, AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, or AutoCAD Mechanical
  2. Determine the installed software version
    In AutoCAD, type 'VER' or 'ABOUT' at the command line, or go to Help > About Autodesk AutoCAD to view the full version number and build number
    Affected if The version falls within these ranges: 2020.x before 2020.1.6, 2021.x before 2021.1.3, 2022.x before 2022.1.3, or 2023.x before 2023.1.1
  3. Verify X_B file handling capability is present
    Check if the application has X_B import/export functionality available; X_B is a binary exchange format commonly used for CAD data transfer
    Affected if The X_B file parsing feature is present and accessible in the installed version (this is a default feature in affected versions)

The system is affected if it runs any of the listed AutoCAD variants (2020, 2021, 2022, or 2023) with a version lower than the patched releases (2020.1.6, 2021.1.3, 2022.1.3, or 2023.1.1 respectively) and has X_B file parsing capability enabled.

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 2020.1.6 / 2021.1.3 / 2022.1.3 or later
Fixed in 2020.1.62021.1.32022.1.3
Interim mitigation

Apply vendor patches from Autodesk for AutoCAD 2022 and 2023. Until patched, exercise caution when opening X_B files from untrusted sources, as malformed files can trigger the out-of-bounds read.

Recommended fix High confidence

AutoCAD 2020.1.6 or later; AutoCAD 2021.1.3 or later; AutoCAD 2022.1.3 or later; 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 currently installed AutoCAD product version by opening AutoCAD and checking 'About AutoCAD' (type ABOUT at the command prompt)
  2. Determine which product line (AutoCAD, AutoCAD Architecture, AutoCAD Civil 3D, etc.) and version year (2020, 2021, 2022, or 2023) is installed
  3. Close all AutoCAD instances and any related applications
  4. Download the appropriate update or install the latest version from the Autodesk Account portal at manage.autodesk.com, or use the Autodesk Access app to check for updates
  5. Install the update matching your product line and version: for 2020 install 2020.1.6 or later; for 2021 install 2021.1.3 or later; for 2022 install 2022.1.3 or later; for 2023 install 2023.1.1 or later
  6. Restart the application and verify the version by typing ABOUT at the command prompt to confirm the installed version includes the security patch
  7. Avoid opening untrusted or unknown .x_b files, as the vulnerability is triggered during parsing of these files
Caveat Standard AutoCAD update considerations apply - ensure custom scripts, plugins, and Hatch patterns are compatible; backup custom files before updating; may require license reactivation

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

Fix this in Autocad Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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