CVE-2024-37002
Multiple Vulnerabilities in the Autodesk AutoCAD Desktop Software
HIGH
7.8
CVSS Score
Published: June 25, 2024 at 03:07 AM UTC
Updated: June 17, 2026 at 07:37 AM UTC
9 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.4%
SSVC
No known exploit
Description
A maliciously crafted MODEL file, when parsed in ASMkern229A.dllthrough Autodesk applications, can be used to uninitialized variables. This vulnerability, along with other vulnerabilities, could lead to code execution in 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.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.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-0009SSVC — 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
StatusANALYZED
CWE
CWE-457CWE-908
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