CVE-2024-37006

Multiple Vulnerabilities in the Autodesk AutoCAD Desktop Software

HIGH
7.8
CVSS Score
Published: June 25, 2024 at 03:15 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 CATPRODUCT file, when parsed in CC5Dll.dll through Autodesk applications, can lead to a memory corruption vulnerability by write access violation. This vulnerability, in conjunction with other vulnerabilities, can 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.

2022 ≤ v < 2022.1.52023 ≤ v < 2023.1.62024 ≤ v < 2024.1.42025 ≤ v < 2025.12022202320242025
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
2022 ≤ v < 2022.1.52023 ≤ v < 2023.1.62024 ≤ v < 2024.1.42025 ≤ v < 2025.12022202320242025
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
2022 ≤ v < 2022.1.52023 ≤ v < 2023.1.62024 ≤ v < 2024.1.42025 ≤ v < 2025.12022202320242025
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
2022 ≤ v < 2022.1.52023 ≤ v < 2023.1.62024 ≤ v < 2024.1.42025 ≤ v < 2025.12022202320242025
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
2022 ≤ v < 2022.1.52023 ≤ v < 2023.1.62024 ≤ v < 2024.1.42025 ≤ v < 2025.12022202320242025
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
2022 ≤ v < 2022.1.52023 ≤ v < 2023.1.62024 ≤ v < 2024.1.42025 ≤ v < 2025.12022202320242025
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
2022 ≤ v < 2022.1.52023 ≤ v < 2023.1.62024 ≤ v < 2024.1.42025 ≤ v < 2025.12022202320242025
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
2022 ≤ v < 2022.1.52023 ≤ v < 2023.1.62024 ≤ v < 2024.1.42025 ≤ v < 2025.12022202320242025
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
2022 ≤ v < 2022.1.52023 ≤ v < 2023.1.62024 ≤ v < 2024.1.42025 ≤ v < 2025.12022202320242025
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 yet

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

SSVC — 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-119CWE-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