CVE-2022-33890
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 · uneditedA maliciously crafted PCT or DWF file when consumed through DesignReview.exe application could lead to memory corruption vulnerability by read access violation. 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 confidenceA specially crafted PCT or DWF file processed by Autodesk DesignReview.exe triggers a memory corruption vulnerability via read access violation. This out-of-bounds memory read can be chained with other vulnerabilities to achieve code execution within the application's process context.
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< 2022.1.3>= 2023.0.0, < 2023.1.1< 2022.1.3>= 2023.0.0, < 2023.1.1< 2022.1.3>= 2023.0.0, < 2023.1.1< 2022.1.3>= 2023.0.0, < 2023.1.1< 2022.1.3>= 2023.0.0, < 2023.1.1< 2022.1.3>= 2023.0.0, < 2023.1.1< 2022.1.3>= 2023.0.0, < 2023.1.1< 2022.1.3>= 2023.0.0, < 2023.1.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate DesignReview.exe on the systemSearch for DesignReview.exe in common installation directories such as C:\Program Files\Autodesk\ or use the command: dir /s C:\DesignReview.exeAffected if DesignReview.exe is found on the system and an affected AutoCAD version is installed
-
Identify installed Autodesk productOpen Windows Settings > Apps & Features or use PowerShell: Get-WmiObject -Class Win32_Product | Select-Object Name, Version to list installed Autodesk productsAffected if Any AutoCAD-based product from the affected product list is installed (Autocad, Autocad Advance Steel, Autocad Architecture, Autocad Civil 3d, Autocad Electrical, Autocad Lt, Autocad Map 3d, or Autocad Mechanical)
-
Determine the exact version of the installed AutoCAD productWithin the installed AutoCAD application, type VERSION at the command prompt, or check the Windows Registry under HKLM\SOFTWARE\Autodesk\AutoCAD\ for the installed version keyAffected if The installed version is less than 2022.1.3, or greater than or equal to 2023.0.0 but less than 2023.1.1
-
Verify if DesignReview component is registeredCheck for DesignReview.exe registration by looking in the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\ or by searching for the file path in the Windows uninstall registry keysAffected if DesignReview.exe is registered as a component of the installed AutoCAD product
A user is affected if DesignReview.exe is present on the system AND their AutoCAD product version falls below 2022.1.3 or between 2023.0.0 and 2023.1.1 inclusive.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2022.1.32023.1.1
Avoid opening untrusted PCT or DWF files in DesignReview.exe. Apply vendor patches when released and run the application with least privileges to limit potential impact.
AutoCAD 2023.1.1 or later (or 2022.1.3 or later for 2022.x versions)
- 1. Verify your current AutoCAD product version by opening the application, clicking the 'Help' menu, and selecting 'About'
- 2. Determine which specific AutoCAD product variant you are using (e.g., AutoCAD, AutoCAD Civil 3D, AutoCAD Electrical, etc.)
- 3. If running version 2022.x or earlier: Upgrade to version 2022.1.3 or later
- 4. If running version 2023.0.0 through 2023.1.0: Upgrade to version 2023.1.1 or later
- 5. Download the appropriate update from the official Autodesk website (www.autodesk.com) under your product's Support section
- 6. Install the update following Autodesk's standard installation procedure
- 7. Verify the installation completed successfully by checking the version number again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33890 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-33890 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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