dbcve.org
AutocadApplication · Autodesk

CVE-2024-37006

HIGH · 7.8 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 2022.1.5 / 2023.1.6 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A memory corruption vulnerability exists in CC5Dll.dll when parsing maliciously crafted CATPRODUCT files in Autodesk applications. The flaw manifests as a write access violation that can be chained with other vulnerabilities to achieve arbitrary code execution within the context of the current process.

MitigationUsers should avoid opening untrusted CATPRODUCT files until Autodesk releases an official patch. Organizations should implement file type validation and sandboxing for affected Autodesk applications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AutocadApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad ArchitectureApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad ElectricalApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad Map 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad MechanicalApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad MepApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Autocad Plant 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1
Civil 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.4>= 2025, < 2025.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Autodesk product and version
    Open the affected application, go to Help > About, or check the Windows Registry under HKLM\SOFTWARE\Autodesk\AutoCAD for the installed version string
    Affected if The version falls within any of these ranges: 2022.x before 2022.1.5, 2023.x before 2023.1.6, 2024.x before 2024.1.4, or 2025.x before 2025.1
  2. Confirm product is among the affected variants
    Determine if the installed product is AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D
    Affected if The product matches any of these eight names with an affected version from step 1
  3. Locate CC5Dll.dll in the application directory
    Search the Autodesk application installation folder for CC5Dll.dll (commonly in the root install directory or bin folder)
    Affected if The file CC5Dll.dll is present on the system
  4. Verify ability to import CATPRODUCT files
    Attempt to open or import a CATPRODUCT file within the application, or check file association settings for .catproduct extension
    Affected if The application can load or import CATPRODUCT files, indicating the vulnerable parsing code path is accessible

You are affected if you run any of the eight listed Autodesk products in the version ranges specified and the application can process CATPRODUCT files using the vulnerable CC5Dll.dll component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2022.1.5 / 2023.1.6 / 2024.1.4 or later
Fixed in 2022.1.52023.1.62024.1.4
Interim mitigation

Users should avoid opening untrusted CATPRODUCT files until Autodesk releases an official patch. Organizations should implement file type validation and sandboxing for affected Autodesk applications.

Recommended fix High confidence

2022.1.5 (for 2022.x), 2023.1.6 (for 2023.x), 2024.1.4 (for 2024.x), or 2025.1 (for 2025.x)

  1. 1. Identify the currently installed Autodesk product version (2022, 2023, 2024, or 2025) by opening the application and navigating to Help > About Autodesk [Product Name].
  2. 2. For AutoCAD 2022 users: Upgrade to version 2022.1.5 or later.
  3. 3. For AutoCAD 2023 users: Upgrade to version 2023.1.6 or later.
  4. 4. For AutoCAD 2024 users: Upgrade to version 2024.1.4 or later.
  5. 5. For AutoCAD 2025 users: Upgrade to version 2025.1 or later.
  6. 6. Download the appropriate update from the Autodesk Account portal at manage.autodesk.com or from the official Autodesk support website.
  7. 7. Close all Autodesk applications before running the installer.
  8. 8. Run the installer and follow the on-screen prompts to complete the update.
Caveat Standard Autodesk update considerations apply - review release notes for your specific version for any changes to features or workflows

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Autocad Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-37006 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data