CVE-2022-33889

HIGH
7.8
CVSS Score
Published: October 3, 2022 at 02:22 PM UTC
Updated: June 17, 2026 at 04:49 AM UTC
11 products affected across 1 vendorAutoCADAutoCAD ElectricalCivil 3D

Using Autodesk® Design Review, Autodesk® Advance Steel, Autodesk® Civil 3D® by N/A?

Get instant alerts when new vulnerabilities affect Autodesk® Design Review, Autodesk® Advance Steel, Autodesk® Civil 3D® - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.4%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2022.1.32023.0.0 ≤ v < 2023.1.1201820222023
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
v < 2022.1.32023.0.0 ≤ v < 2023.1.1
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
v < 2022.1.32023.0.0 ≤ v < 2023.1.1
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
v < 2022.1.32023.0.0 ≤ v < 2023.1.1
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
v < 2022.1.32023.0.0 ≤ v < 2023.1.1
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
v < 2022.1.32023.0.0 ≤ v < 2023.1.1
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
v < 2022.1.32023.0.0 ≤ v < 2023.1.1
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
v < 2022.1.32023.0.0 ≤ v < 2023.1.1
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
v < 2022.1.32023.0.0 ≤ v < 2023.1.1
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
v < 2022.1.32023.0.0 ≤ v < 2023.1.1201820222023
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card