dbcve.org
AutocadApplication · Autodesk

CVE-2022-42938

HIGH · 7.8 CVSS v3.1 Published 2022-10-21
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
81/100
Remediation priority · High
No privileges Patch available

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 TGA file when consumed through DesignReview.exe application could lead to memory corruption vulnerability. 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
How this class of weakness works · CWE-787

The program writes past the bounds of a buffer, overwriting adjacent memory an attacker can turn to their advantage. Crafted input can overwrite control data and redirect execution. Remediation is validating every index and length before a write, plus modern memory-safety mitigations.

General guidance for the out-of-bounds write class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:= 2019= 2020= 2021= 2022= 2023
Autocad Advance SteelApplication
Affected:= 2019= 2020= 2021= 2022= 2023
Autocad ArchitectureApplication
Affected:= 2019= 2020= 2021= 2022= 2023
Autocad Civil 3dApplication
Affected:= 2019= 2020= 2021= 2022= 2023
Autocad ElectricalApplication
Affected:= 2019= 2020= 2021= 2022= 2023
Autocad LtApplication
Affected:= 2019= 2020= 2021= 2022= 2023
Autocad Map 3dApplication
Affected:= 2019= 2020= 2021= 2022= 2023
Autocad MechanicalApplication
Affected:= 2019= 2020= 2021= 2022= 2023

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

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
Patch available Apply the vendor patch
Vendor patch www.autodesk.com →
Recommended fix High confidence

Upgrade to the fixed release specified in Autodesk Security Advisory ADSK-SA-2022-0004 (typically version 2023 or later, or the specific patch version noted in the advisory)

  1. Navigate to the official Autodesk security advisory at https://www.autodesk.com/trust/security-advisories/adsk-sa-2022-0004 to obtain the specific patch or fixed version
  2. Identify the exact build/version number of your currently installed Autodesk product (AutoCAD or specific vertical)
  3. Upgrade to the fixed version as specified in the security advisory - this will typically be a later version (2023 or newer) or a specific patch that addresses the vulnerability
  4. Verify the upgrade by checking the DesignReview.exe component version matches the patched release
  5. Test the TGA file processing functionality in the updated version to confirm the vulnerability is resolved
  6. Ensure the upgraded version is also supported under your Autodesk subscription/maintenance agreement
Caveat Review Autodesk's support lifecycle for your product version; ensure your subscription is current to receive patches; some older features or workflows may behave differently in newer versions

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

We can apply and verify the patch for your build — typical engagement from $3,200. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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