dbcve.org
AutocadApplication · Autodesk

CVE-2024-23147

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, X_B and STEP, when parsed in ASMKERN228A.dll and ASMKERN229A.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 Autodesk's ASMKERN228A.dll and ASMKERN229A.dll libraries when parsing maliciously crafted CATPART, X_B, and STEP CAD files. The vulnerability triggers a write access violation that can be chained with other vulnerabilities to achieve code execution in the context of the current process.

MitigationApply the vendor patch or update from Autodesk to obtain corrected versions of the affected parsing libraries. Until patched, avoid opening untrusted CAD files from unknown 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:>= 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 Windows Control Panel > Programs and Features, or check the registry at HKLM\SOFTWARE\Autodesk\AutoCAD for the product name and version
    Affected if The product is one of AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D
  2. Get installed version number
    Run 'reg query HKLM\SOFTWARE\Autodesk\AutoCAD /v Version' or right-click the installed application in Programs and Features to view the version
    Affected if The version falls within any of these ranges: 2022.0 to 2022.1.4, 2023.0 to 2023.1.5, 2024.0 to 2024.1.3, or 2025.0 to 2025.0 (all versions below the fixed releases)
  3. Locate the affected DLL files
    Search for ASMKERN228A.dll or ASMKERN229A.dll in the application installation directory (typically C:\Program Files\Autodesk\<ProductName>\)
    Affected if The DLL files exist in the installation folder, indicating the vulnerable parsing module is present
  4. Confirm file type association or recent usage
    Check recent documents or file associations for .CATPART, .X_B, or .STEP files opened by the installed Autodesk product
    Affected if The product has been used to open or is associated with CATPART, X_B, or STEP file types, enabling the attack surface

A user is affected if they have any of the listed Autodesk products installed with a version between 2022 and the fixed releases (2022.1.5, 2023.1.6, 2024.1.4, or 2025.1), as the vulnerable ASMKERN228A.dll/ASMKERN229A.dll libraries are present and the affected file parsers are available.

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 the vendor patch or update from Autodesk to obtain corrected versions of the affected parsing libraries. Until patched, avoid opening untrusted CAD files from unknown sources.

Recommended fix High confidence

Upgrade to AutoCAD 2022.1.5+, 2023.1.6+, 2024.1.4+, or 2025.1+ (and corresponding versions for vertical products and Civil 3D)

  1. Identify the exact version of the installed Autodesk product (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D) by opening the application and navigating to Help > About Autodesk.
  2. Close all Autodesk applications completely before proceeding with the update.
  3. Download the appropriate update or installer for your product version from the official Autodesk website (www.autodesk.com) or through your Autodesk Account portal.
  4. For AutoCAD 2022: Upgrade to version 2022.1.5 or later.
  5. For AutoCAD 2023: Upgrade to version 2023.1.6 or later.
  6. For AutoCAD 2024: Upgrade to version 2024.1.4 or later.
  7. For AutoCAD 2025: Upgrade to version 2025.1 or later.
  8. Apply the same version upgrades to any specialized AutoCAD verticals (Architecture, Electrical, Mechanical, MEP, Plant 3D) and Civil 3D as listed in the affected versions.
Caveat Review Autodesk's release notes for your specific version upgrade for any workflow changes or deprecated features; ensure compatibility with any custom scripts or third-party plugins

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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