dbcve.org
AutocadApplication · Autodesk

CVE-2024-23123

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 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 · high confidence

An out-of-bounds write vulnerability exists in Autodesk AutoCAD's CC5Dll.dll and ASMBASE228A.dll when parsing maliciously crafted CATPART files. The vulnerability allows writing data beyond allocated buffer boundaries, potentially leading to crash, data corruption, or arbitrary code execution in the context of the current process.

MitigationApply vendor patches from Autodesk for affected AutoCAD versions; avoid opening untrusted CATPART files from unknown or untrusted sources.

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 AutoCAD or vertical product, go to Help > About Autodesk. Alternatively, check Program Files for the product folder name (e.g., Autodesk AutoCAD 2024, Autodesk AutoCAD Architecture 2024, etc.)
    Affected if Product is AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel
  2. Determine installed version and build number
    In AutoCAD, type VER or INFOCONFIG at the command line, or check Help > About Autodesk. Note both the year (2021-2025) and the full version number (e.g., 2024.1.2)
    Affected if Version falls within: 2021 to 2021.1.3, 2022 to 2022.1.3, 2023 to 2023.1.4, 2024 to 2024.1.2, or 2025 to 2025.0.0
  3. Locate vulnerable DLL files
    Search for CC5Dll.dll and ASMBASE228A.dll in the product installation directory (typically C:\Program Files\Autodesk\<ProductName>\<Version>). Note their file versions by right-clicking > Properties > Details
    Affected if DLLs exist in the installation folder and their file version is lower than the patched version for your product year
  4. Check if CATPART import capability is active
    Open AutoCAD and attempt to import or open a CATPART file using the INSERT command or by using a design center feature that loads 3D part data. The vulnerability triggers when these files are parsed
    Affected if User can import or open CATPART files and the vulnerable DLLs are loaded into memory

You are affected if you have any of the listed products installed with version 2021 through the versions just before 2021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, or 2025.0.1, and you use CATPART file import functionality.

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 vendor patches from Autodesk for affected AutoCAD versions; avoid opening untrusted CATPART files from unknown or untrusted sources.

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. 1. Identify the exact Autodesk product and version currently installed (e.g., AutoCAD 2023, Civil 3D 2022, etc.)
  2. 2. Close any running instances of the affected Autodesk application
  3. 3. Download the appropriate update from Autodesk's official support website: https://www.autodesk.com/support/technical-center/articles
  4. 4. For AutoCAD 2021: Apply update 2021.1.4 or later
  5. 5. For AutoCAD 2022: Apply update 2022.1.4 or later
  6. 6. For AutoCAD 2023: Apply update 2023.1.5 or later
  7. 7. For AutoCAD 2024: Apply update 2024.1.3 or later
  8. 8. Restart the application after installing the update
Caveat Standard Autodesk update - review release notes for any changes to features or workflows that may affect existing projects

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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