CVE-2022-33884
HIGH
7.5
CVSS Score
Published: October 3, 2022 at 02:24 PM UTC
Updated: June 17, 2026 at 04:49 AM UTC
10 products affected across 1 vendorAutoCADAutoCAD ElectricalCivil 3D
Using utodesk® AutoCAD®, Advance Steel and Civil 3D® by N/A?
Get instant alerts when new vulnerabilities affect utodesk® AutoCAD®, Advance Steel and Civil 3D® - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 3%
Description
Parsing a maliciously crafted X_B file can force Autodesk AutoCAD 2023 and 2022 to read beyond allocated boundaries. This vulnerability in conjunction with other vulnerabilities could lead to code execution in the context of the current process.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
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
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
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
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
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
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
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
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
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
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
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
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
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
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
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
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
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
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
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 yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
References (1)
x_refsource_MISCVendor Advisory
Source: [email protected]
https://www.autodesk.com/trust/security-advisories/adsk-sa-2022-0020CVSS
- Attack Vector
- NETWORK
- Complexity
- LOW
- Privileges
- NONE
- User Interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality
- HIGH
- Integrity
- NONE
- Availability
- NONE
Vector?
Quick Info
StatusMODIFIED
CWE
CWE-125
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