CVE-2024-9997
Autodesk AutoCAD DWG File Parsing Memory Corruption Code Execution Vulnerability
HIGH
7.8
CVSS Score
Published: October 29, 2024 at 09:45 PM UTC
Updated: June 17, 2026 at 08:25 AM UTC
13 products affected across 1 vendorAutoCADAutoCAD ElectricalCivil 3D
Using AutoCAD by Autodesk?
Get instant alerts when new vulnerabilities affect AutoCAD - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit
Description
A maliciously crafted DWG file when parsed in acdb25.dll through Autodesk AutoCAD can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to cause a crash, write sensitive data, or execute arbitrary code 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 2022.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.1, so it looks safe — our inference, not a vendor statement
2025 ≤ v < 2025.1.1
Affected range stops below 2025.1.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.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)
Vendor Advisory
Source: [email protected]
https://www.autodesk.com/trust/security-advisories/adsk-sa-2024-0021SSVC — Action Prioritization
SSVCNo known exploitNot automatableTotal impact
SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.
CVSS
7.8HIGHautodesk
- Attack Vector
- LOCAL
- Complexity
- LOW
- Privileges
- NONE
- User Interaction
- REQUIRED
- Scope
- UNCHANGED
- Confidentiality
- HIGH
- Integrity
- HIGH
- Availability
- HIGH
Vector?
Quick Info
StatusMODIFIED
CWE
CWE-120CWE-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