dbcve.org
AutocadApplication · Autodesk

CVE-2022-33889

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 GIF or JPEG files when parsed through Autodesk Design Review 2018, and AutoCAD 2023 and 2022 could be used to write beyond the allocated heap buffer. This vulnerability could lead to arbitrary code execution.

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 heap buffer overflow vulnerability in Autodesk Design Review 2018 and AutoCAD 2022/2023 allows parsing of maliciously crafted GIF or JPEG files to write beyond allocated heap memory, enabling arbitrary code execution.

MitigationApply vendor-provided security patches from Autodesk for Design Review 2018, AutoCAD 2022, and AutoCAD 2023 to remediate this heap overflow vulnerability.

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.1.3>= 2023.0.0, < 2023.1.1
Autocad Advance SteelApplication
Affected:< 2022.1.3>= 2023.0.0, < 2023.1.1
Autocad ArchitectureApplication
Affected:< 2022.1.3>= 2023.0.0, < 2023.1.1
Autocad Civil 3dApplication
Affected:< 2022.1.3>= 2023.0.0, < 2023.1.1
Autocad ElectricalApplication
Affected:< 2022.1.3>= 2023.0.0, < 2023.1.1
Autocad LtApplication
Affected:< 2022.1.3>= 2023.0.0, < 2023.1.1
Autocad Map 3dApplication
Affected:< 2022.1.3>= 2023.0.0, < 2023.1.1
Autocad MechanicalApplication
Affected:< 2022.1.3>= 2023.0.0, < 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 Autodesk product
    Check Windows registry under HKLM\SOFTWARE\Autodesk\AutoCAD or look for AutoCAD installation folders (typically C:\Program Files\Autodesk\AutoCAD)
    Affected if Any AutoCAD variant (AutoCAD, AutoCAD Architecture, AutoCAD Civil 3D, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, Advance Steel) or Design Review 2018 is installed
  2. Retrieve installed version
    Run ' acad.exe -version ' from the AutoCAD installation directory, or check the version in the registry key HKLM\SOFTWARE\Autodesk\AutoCAD\<version>\Settings\Release
    Affected if Version cannot be determined or shows a 2022/2023 release
  3. Compare version against affected ranges
    Check if the version is: < 2022.1.3 (any 2022 release before update 1.3), OR >= 2023.0.0 but < 2023.1.1 (any 2023 release before update 1.1)
    Affected if Installed version falls within < 2022.1.3 OR (>= 2023.0.0 AND < 2023.1.1)
  4. Confirm vulnerability trigger condition
    This vulnerability is triggered when processing maliciously crafted GIF or JPEG files. Check if the application is used to open or preview image files
    Affected if Users can open or preview GIF/JPEG files within the affected AutoCAD application

The environment is affected if any Autodesk AutoCAD variant (or Design Review 2018) is installed with a version below 2022.1.3 or between 2023.0.0 and 2023.1.1, and users can process image files in the application.

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-provided security patches from Autodesk for Design Review 2018, AutoCAD 2022, and AutoCAD 2023 to remediate this heap overflow vulnerability.

Recommended fix High confidence

AutoCAD 2022.1.3 or later; AutoCAD 2023.1.1 or later (depending on your product line)

  1. 1. Open Autodesk Account or Autodesk Desktop Connector to check for available updates
  2. 2. Navigate to the Updates section for your installed Autodesk product
  3. 3. Download and install the update matching your product line: For AutoCAD 2022.x and variants, install version 2022.1.3 or later; For AutoCAD 2023.x and variants, install version 2023.1.1 or later
  4. 4. Alternatively, download updates directly from https://www.autodesk.com/support-downloads (search for your specific product)
  5. 5. Restart the application after installation completes
  6. 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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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