dbcve.org
Autocad ElectricalApplication · Autodesk

CVE-2024-23136

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 STP file in ASMKERN228A.dll when parsed through Autodesk applications can be used to dereference an untrusted pointer. This vulnerability, along with other vulnerabilities, could lead to code execution in 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

A memory corruption vulnerability in ASMKERN228A.dll allows dereferencing of an untrusted pointer when parsing maliciously crafted STP (STEP CAD) files in Autodesk applications, potentially enabling code execution within the current process context.

MitigationApply vendor-supplied patches for affected Autodesk products; enforce file origin policies and scan STP files from untrusted sources before opening.

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
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
Autocad Map 3dApplication
Affected:>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1
AutocadApplication
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 the application and go to Help > About Autodesk [Product Name], or check Add/Remove Programs for installed Autodesk software
    Affected if Any of the following products are installed: AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, Advance Steel, AutoCAD Map 3D, or AutoCAD
  2. Check product version number
    In the application, type 'VER' at the command line or go to Help > About > Product Information to display the exact version and release number
    Affected if Version falls within: 2021 (any build < 2021.1.4), 2022 (any build < 2022.1.4), 2023 (any build < 2023.1.5), 2024 (any build < 2024.1.3), or 2025 (any build < 2025.0.1)
  3. Locate ASMKERN228A.dll
    Search for ASMKERN228A.dll in the application installation directory (typically C:\Program Files\Autodesk\[ProductName]\[Version]\)
    Affected if The DLL exists in the installation folder - its presence indicates the vulnerable component is loaded
  4. Verify file handling of STP files
    Confirm the product can open or import STEP (.stp) files - attempt to import a known STP file or check file association settings
    Affected if STP file import capability is enabled or available in the installation

The environment is affected if any listed Autodesk product is installed with a version that falls below the patched releases (2021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, or 2025.0.1) and the application can import STEP files.

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-supplied patches for affected Autodesk products; enforce file origin policies and scan STP files from untrusted sources before opening.

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 (select the appropriate minimum version based on the product line)

  1. 1. Identify the specific Autodesk product and version currently installed (e.g., AutoCAD 2023, Civil 3D 2024, etc.)
  2. 2. Close any running Autodesk applications
  3. 3. Obtain the appropriate update from the Autodesk Account portal or the Autodesk Desktop App
  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. Apply the same corresponding updates for any other affected Autodesk products installed (Electrical, Mechanical, MEP, Plant 3D, Civil 3D, Advance Steel, Map 3D)
Caveat Standard Autodesk update - ensure project files are backed up before updating; review Autodesk's update release notes for any specific compatibility notes

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

Fix this in Autocad Electrical Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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