dbcve.org
AutocadApplication · Autodesk

CVE-2022-33886

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 maliciously crafted MODEL and SLDPRT file can be used to write beyond the allocated buffer while parsing through Autodesk AutoCAD 2023, 2022, 2021, 2020, and Maya 2023 and 2022. The vulnerability exists because the application fails to handle crafted MODEL and SLDPRT files, which causes an unhandled exception. A malicious actor could leverage this vulnerability 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 · moderate confidence

Buffer overflow vulnerability in Autodesk AutoCAD and Maya when parsing maliciously crafted MODEL and SLDPRT files. The application fails to properly validate input during file parsing, allowing write-beyond-buffer conditions that trigger unhandled exceptions and could enable arbitrary code execution.

MitigationApply vendor security updates for affected AutoCAD (2020-2023) and Maya (2022-2023) versions. Until patches are applied, avoid opening MODEL or SLDPRT files from untrusted 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
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 installed AutoCAD product variant
    Open AutoCAD, go to Help > About Autodesk AutoCAD, or check the application title bar for product name (e.g., AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, or Advance Steel)
    Affected if The product is any of the AutoCAD variants listed in the affected versions
  2. Check installed AutoCAD version number
    In AutoCAD, type 'VER' or 'ABOUT' at the command line, or check Help > About Autodesk AutoCAD. Note the full version (e.g., 2022.1.2, 2023.1.0)
    Affected if Version is 2022.x where x < 1.3, OR version is 2023.x where x < 1.1
  3. Verify if MODEL or SLDPRT file parsing is used
    Check if users routinely open or import MODEL files (common in mechanical/design workflows) or SLDPRT files (SolidWorks part files) within the AutoCAD environment
    Affected if The application is used to open or process MODEL or SLDPRT files from any source
  4. Review AutoCAD security settings
    Check for any trusted location settings (OPTIONS command > Files tab > Trusted locations) and security settings (OPTIONS command > Security tab)
    Affected if Untrusted files can be opened without restrictions or warnings

A user is affected if they run any AutoCAD variant (Architecture, Civil 3D, Electrical, LT, Map 3D, Mechanical, or Advance Steel) with version 2022.x before 1.3 or version 2023.x before 1.1, and the application parses MODEL or SLDPRT 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 2022.1.3 / 2023.1.1 or later
Fixed in 2022.1.32023.1.1
Interim mitigation

Apply vendor security updates for affected AutoCAD (2020-2023) and Maya (2022-2023) versions. Until patches are applied, avoid opening MODEL or SLDPRT files from untrusted sources.

Recommended fix High confidence

AutoCAD 2022.1.3 or later; AutoCAD 2023.1.1 or later (and corresponding versions for affected variants)

  1. 1. Ensure you have a backup of all critical AutoCAD drawings and custom settings
  2. 2. Close any running instances of AutoCAD or related products (AutoCAD Architecture, Civil 3D, Electrical, Mechanical, Map 3D, LT, Advance Steel)
  3. 3. For AutoCAD 2022 users: Upgrade to version 2022.1.3 or later
  4. 4. For AutoCAD 2023 users: Upgrade to version 2023.1.1 or later
  5. 5. For other listed AutoCAD variants (Architecture, Civil 3D, Electrical, Mechanical, Map 3D, LT, Advance Steel): Apply the corresponding version update matching your product line (2022.1.3 for 2022 products, 2023.1.1 for 2023 products)
  6. 6. Download updates from the official Autodesk website or use the Autodesk Access application to check for updates
  7. 7. Install the update following Autodesk's standard installation procedure
  8. 8. Verify the update was successful by checking the About AutoCAD dialog for the installed version number

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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