dbcve.org
AutocadApplication · Autodesk

CVE-2024-23124

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, when parsed in ASMIMPORT228A.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

This is an out-of-bounds write vulnerability in the ASMIMPORT228A.dll library of Autodesk AutoCAD when parsing STP (STEP CAD exchange format) files. A specially crafted malicious STP file can trigger memory corruption leading to crash, data corruption, or arbitrary code execution in the context of the current process.

MitigationApply the vendor patch from Autodesk when available. Until then, avoid opening STP files from untrusted sources and consider disabling STP file import functionality or running AutoCAD in a sandboxed environment.

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 AutoCAD product and version
    Open AutoCAD and type 'VER' or 'ABOUT' in the command line, or check the Help > About dialog. For command-line: type 'VER' and press Enter. The version number will display in theAbout window.
    Affected if The version displayed falls within any of these ranges: 2021 (versions < 2021.1.4), 2022 (versions < 2022.1.4), 2023 (versions < 2023.1.5), 2024 (versions < 2024.1.3), 2025 (versions < 2025.0.1)
  2. Locate the vulnerable ASMIMPORT228A.dll library
    Search for ASMIMPORT228A.dll in the AutoCAD installation directory, typically found under C:\Program Files\Autodesk\AutoCAD [VERSION]\ or C:\Program Files\Autodesk\AutoCAD [VERSION]\Support\. Use File Explorer search or run: dir /s C:\ "ASMIMPORT228A.dll"
    Affected if The DLL exists in the AutoCAD installation folder and its version is older than the patched version for your AutoCAD release.
  3. Confirm AutoCAD variant (Architecture, Electrical, Mechanical, MEP, Plant 3D, Civil 3D, or Advance Steel)
    Check the product name in the Help > About dialog or the application shortcut. The variant name appears in the title bar or About window.
    Affected if The installed product is any AutoCAD variant listed (AutoCAD Architecture, Electrical, Mechanical, MEP, Plant 3D, Civil 3D, or Advance Steel) and the version matches the affected ranges.
  4. Determine if STP file import is used or available
    In AutoCAD, try importing a STEP file: type 'IMPORT' or 'STPIMPORT' in the command line, or check if the STEP file format is listed in the Files of Type dropdown when using the IMPORT command. You can also check for any registered STEP import functionality in the application.
    Affected if STP/STEP file import functionality is present and available in the installation.

Your environment is affected if you have any AutoCAD 2021-2025 variant installed with a version lower than the patched releases (2021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, or 2025.0.1) and the ASMIMPORT228A.dll library exists 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 from Autodesk when available. Until then, avoid opening STP files from untrusted sources and consider disabling STP file import functionality or running AutoCAD in a sandboxed environment.

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. For all versions, moving to the latest available release is recommended.

  1. Open Autodesk Account or use the Autodesk Desktop App to check for available updates
  2. Navigate to the Autodesk Account management portal at account.autodesk.com
  3. Locate the affected product (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel)
  4. Download the update for your specific version year: For 2021.x download 2021.1.4 or later; For 2022.x download 2022.1.4 or later; For 2023.x download 2023.1.5 or later; For 2024.x download 2024.1.3 or later
  5. Alternatively, open the product and go to Help > Check for Updates to trigger automatic update detection
  6. Close all Autodesk applications before installing the update
  7. Run the downloaded installer with administrator privileges
  8. Follow the on-screen installation prompts to complete the update
Caveat Autodesk minor updates and service packs typically maintain backward compatibility with drawing files; however, verify critical custom scripts, plugins, and LSP add-ins work with the new version before deploying organization-wide.

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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