AutocadApplication · Autodesk

CVE-2022-33887

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 PDF file when parsed through Autodesk AutoCAD 2023 causes an unhandled exception. An attacker can leverage this vulnerability to cause a crash or read sensitive data or execute arbitrary code 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 · moderate confidence

A maliciously crafted PDF file parsed by Autodesk AutoCAD 2023 triggers an unhandled exception that can lead to arbitrary code execution in the current process context. The vulnerability stems from improper handling of malformed PDF structures during the parsing process.

MitigationApply the vendor patch for AutoCAD 2023 when available; until then, avoid opening untrusted or unexpected PDF files in AutoCAD and disable PDF integration if not required.

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
    Open AutoCAD and go to Help > About Autodesk AutoCAD, or run the app and check the title bar/splash screen for the product name (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. Check installed version number
    Run the VER command in AutoCAD, or look at the version info in Help > About AutoCAD. Note the full version number (e.g., 2022.0, 2022.1.2, 2023.0, 2023.1.0)
    Affected if Version is 2022.x where x is less than 1.3, OR version is 2023.x where x is less than 1.1 (i.e., versions 2022.0 through 2022.1.2, or 2023.0 through 2023.1.0)
  3. Confirm PDF integration is in use
    Check if PDF import/export or PDF underlay features are enabled by typing PDFATTACH or PDFIMPORT at the AutoCAD command prompt. If these commands are available, PDF integration is present
    Affected if PDFATTACH or PDFIMPORT commands are functional and available in the installation

The environment is affected if an AutoCAD variant (2022.x before 1.3 or 2023.x before 1.1) is installed with PDF integration features enabled and the user opens a malicious PDF file.

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 patch for AutoCAD 2023 when available; until then, avoid opening untrusted or unexpected PDF files in AutoCAD and disable PDF integration if not required.

Recommended fix High confidence

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

  1. 1. Close any running AutoCAD instances
  2. 2. Ensure you have a backup of your work and settings
  3. 3. For AutoCAD 2022.x: Upgrade to version 2022.1.3 or later
  4. 4. For AutoCAD 2023.x: Upgrade to version 2023.1.1 or later
  5. 5. Download the appropriate update from the Autodesk Account portal or use the Autodesk Access application
  6. 6. Run the installer with administrator privileges
  7. 7. Follow the on-screen installation prompts
  8. 8. Restart AutoCAD after the update completes
Caveat Standard Autodesk update considerations apply - some older drawing features or third-party plugins may require updates for compatibility with newer versions

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-33887 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-33887 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