dbcve.org
AutocadApplication · Autodesk

CVE-2024-23144

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 CATPART file, when parsed in CC5Dll.dll and ASMBASE228A.dll through Autodesk AutoCAD, may force an Out-of-Bounds Write vulnerability. A malicious actor may leverage this vulnerability to cause a crash, cause data corruption, 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 · moderate confidence

An out-of-bounds write vulnerability exists in CC5Dll.dll and ASMBASE228A.dll when parsing maliciously crafted CATPART files in Autodesk AutoCAD. The vulnerability allows memory corruption that can be leveraged for denial of service, data corruption, or arbitrary code execution in the context of the current process.

MitigationApply vendor patches from Autodesk when available. Until then, exercise caution with CATPART files from untrusted sources and consider application whitelisting to block potentially malicious file types.

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
    Open Control Panel > Programs and Features, or run 'reg query "HKLM\SOFTWARE\Autodesk\AutoCAD"' to list installed Autodesk products and versions
    Affected if No Autodesk product is found in the listed affected products (AutoCAD 2022-2025 or its vertical products)
  2. Determine exact version of AutoCAD
    Run 'reg query "HKLM\SOFTWARE\Autodesk\AutoCAD\[Version]" /v Version' replacing [Version] with the installed version key (e.g., AC27-1), or check Help > About in AutoCAD
    Affected if The version falls within any of these ranges: >= 2022 and < 2022.1.5; >= 2023 and < 2023.1.6; >= 2024 and < 2024.1.4; >= 2025 and < 2025.1
  3. Locate vulnerable DLL files
    Search for CC5Dll.dll and ASMBASE228A.dll in the AutoCAD installation directory (typically C:\Program Files\Autodesk\AutoCAD[Version])
    Affected if Either CC5Dll.dll or ASMBASE228A.dll exists in the AutoCAD program folder, indicating the vulnerable component is present
  4. Confirm CATPART import capability
    Check if the CATIA importer is available by attempting to open a CATPART file, or verify the presence of import-related DLLs or plugins in the AutoCAD plug-ins folder
    Affected if CATPART file import functionality is enabled or available in the installation

You are affected if you have AutoCAD (or Architecture/Electrical/Map 3D/Mechanical/MEP/Plant 3D/Civil 3D) versions 2022 through the listed patch levels AND the vulnerable DLLs (CC5Dll.dll or ASMBASE228A.dll) are present on your system, meaning parsing a malicious CATPART file could trigger the out-of-bounds write vulnerability.

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

Apply vendor patches from Autodesk when available. Until then, exercise caution with CATPART files from untrusted sources and consider application whitelisting to block potentially malicious file types.

Recommended fix High confidence

AutoCAD 2022.1.5+ | AutoCAD 2023.1.6+ | AutoCAD 2024.1.4+ | AutoCAD 2025.1+ (and corresponding versions for Architecture, Electrical, Map 3D, Mechanical, MEP, Plant 3D, Civil 3D)

  1. 1. Identify the exact AutoCAD-based product and version currently installed (e.g., AutoCAD 2023.1, AutoCAD Architecture 2024.0, Civil 3D 2023.1, etc.).
  2. 2. Close any running instances of the affected Autodesk application.
  3. 3. Verify the current installed version by opening the application, clicking the Application menu, and selecting 'About AutoCAD' or the equivalent for your product.
  4. 4. Download the appropriate fixed version from the Autodesk Account portal (account.autodesk.com) or through your organization's software distribution method.
  5. 5. For each affected product version, apply the following minimum updates: AutoCAD 2022 to 2022.1.5 or later; AutoCAD 2023 to 2023.1.6 or later; AutoCAD 2024 to 2024.1.4 or later; AutoCAD 2025 to 2025.1 or later. Same version requirements apply to AutoCAD Architecture, Electrical, Map 3D, Mechanical, MEP, Plant 3D, and Civil 3D.
  6. 6. Run the installer with appropriate administrative privileges.
  7. 7. Restart the workstation after installation completes.
  8. 8. Verify the updated version by checking 'About' dialog to confirm the installed version matches or exceeds the fixed versions listed above.
Caveat Upgrading may introduce changes to UI, workflow, or require revalidation of custom scripts/LISP routines; review Autodesk release notes for the target version before deployment in production environments.

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $2,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23144 — 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-23144 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