dbcve.org
AutocadApplication · Autodesk

CVE-2024-23126

HIGH · 7.8 CVSS v3.1 Published 2024-02-22
Fix available
A fix is available. Upgrade to 2021.1.4 / 2022.1.4 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 CATPART file when parsed CC5Dll.dll through Autodesk applications can be used to cause a Stack-based Overflow. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code 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 stack-based buffer overflow vulnerability exists in CC5Dll.dll when parsing maliciously crafted CATPART files. The parsing logic fails to properly validate input bounds before copying data onto the stack, allowing an attacker to overwrite return addresses and potentially execute arbitrary code in the context of the current process.

MitigationApply the vendor patch for CVE-2024-23126 when available. Until then, implement input validation and replace unsafe string operations (strcpy, sprintf, etc.) with bounds-checked alternatives (strncpy, snprintf) in the CATPART parsing code within CC5Dll.dll.

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:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad ArchitectureApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad ElectricalApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad MechanicalApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad MepApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Autocad Plant 3dApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Civil 3dApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
Advance SteelApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.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
    Open Windows Control Panel > Programs and Features, or use 'Get-ItemProperty' in PowerShell for registry keys under HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to find which Autodesk application is installed.
    Affected if The installed product is one of: Autocad, Autocad Architecture, Autocad Electrical, Autocad Mechanical, Autocad Mep, Autocad Plant 3d, Civil 3d, or Advance Steel.
  2. Determine installed product version
    In the software, go to Help > About Autodesk [Product], or check the version in Control Panel > Programs and Features under the Version column, or run: (Get-ItemProperty 'HKLM:\SOFTWARE\Autodesk\AutoCAD\<version>').ReleaseName
    Affected if The version falls within any of these vulnerable ranges: >= 2021 and < 2021.1.4; >= 2022 and < 2022.1.4; >= 2023 and < 2023.1.5; >= 2024 and < 2024.1.3; >= 2025 and < 2025.0.1.
  3. Locate CC5Dll.dll on the system
    Search for CC5Dll.dll using PowerShell: Get-ChildItem -Path 'C:\Program Files\Autodesk' -Recurse -Filter 'CC5Dll.dll' -ErrorAction SilentlyContinue | Select-Object FullName, Length, LastWriteTime
    Affected if The DLL exists in any Autodesk installation directory, confirming the vulnerable component is present.
  4. Verify the DLL version if possible
    Right-click the found CC5Dll.dll, select Properties, and check the Details tab for File Version and Product Version, or run: (Get-ItemProperty 'Path\to\CC5Dll.dll').VersionInfo
    Affected if The DLL version is not available or cannot be verified through standard Windows properties.

You are affected if you have any of the listed Autodesk products installed with a version between 2021 and the respective patched version (2021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, or 2025.0.1) and the CC5Dll.dll component is present on the system.

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 2021.1.4 / 2022.1.4 / 2023.1.5 or later
Fixed in 2021.1.42022.1.42023.1.5
Interim mitigation

Apply the vendor patch for CVE-2024-23126 when available. Until then, implement input validation and replace unsafe string operations (strcpy, sprintf, etc.) with bounds-checked alternatives (strncpy, snprintf) in the CATPART parsing code within CC5Dll.dll.

Recommended fix High confidence

Upgrade to version 2021.1.4 or later for 2021 products; 2022.1.4 or later for 2022 products; 2023.1.5 or later for 2023 products; 2024.1.3 or later for 2024 products

  1. Identify the installed Autodesk product version by opening the application and navigating to Help > About Autodesk [Product Name]
  2. Download the appropriate security update from the Autodesk website or use the Autodesk Access application to check for updates
  3. For AutoCAD 2021 users: Upgrade to version 2021.1.4 or later
  4. For AutoCAD 2022 users: Upgrade to version 2022.1.4 or later
  5. For AutoCAD 2023 users: Upgrade to version 2023.1.5 or later
  6. For AutoCAD 2024 users: Upgrade to version 2024.1.3 or later
  7. Apply the same version upgrades to any specialized verticals (Architecture, Electrical, Mechanical, MEP, Plant 3D, Civil 3D, Advance Steel) matching the base AutoCAD version
  8. Restart the application after applying the update
Caveat Minor: Standard Autodesk update process; verify custom scripts/lisp routines remain compatible with the new version

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-23126 — 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-23126 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