dbcve.org
AutocadApplication · Autodesk

CVE-2024-23120

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 and STEP file, when parsed in ASMIMPORT228A.dll and ASMIMPORT229A.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

A file parsing vulnerability in Autodesk AutoCAD's ASMIMPORT228A.dll and ASMIMPORT229A.dll libraries allows out-of-bounds memory writes when parsing maliciously crafted STP or STEP CAD files. This memory corruption can be leveraged for denial of service, data corruption, or arbitrary code execution within the current process context.

MitigationApply the vendor security update from Autodesk to patch the vulnerable ASMIMPORT DLLs. Consider implementing file type validation or sandboxing for untrusted STP/STEP files until the patch is deployed.

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 the installed Autodesk product
    Open the application and go to Help > About Autodesk, or check Add/Remove Programs for the installed Autodesk product name
    Affected if The product is one of: AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel
  2. Determine the installed version number
    In the application, type 'VER' or 'ABOUT' at the command line and press Enter, or check the program version in Add/Remove Programs
    Affected if The version is 2021.x, 2022.x, 2023.x, 2024.x, or 2025.x (any release within these years)
  3. Compare the version to affected ranges
    Match the full version (for example 2023.1.4) against the vulnerable ranges: 2021.0 to 2021.1.3, 2022.0 to 2022.1.3, 2023.0 to 2023.1.4, 2024.0 to 2024.1.2, 2025.0
    Affected if The installed version is less than 2021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, or 2025.0.1 for the respective year
  4. Locate the ASMIMPORT DLL files
    Search the installation directory (commonly C:\Program Files\Autodesk\) for files named ASMIMPORT228A.dll or ASMIMPORT229A.dll using File Explorer or the 'dir' command
    Affected if Either ASMIMPORT228A.dll or ASMIMPORT229A.dll exists in the product installation folder
  5. Check if STEP/STP file import is used
    Open the application and verify if the STEP import functionality is accessible (typically via INSERT > Import > STEP or similar menu path)
    Affected if The application can import or open STEP/STP CAD files

You are affected if you have any of the listed Autodesk products installed with version 2021 through 2024.x (before the fixed releases) or 2025.0, and the ASMIMPORT DLL is present on your 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 security update from Autodesk to patch the vulnerable ASMIMPORT DLLs. Consider implementing file type validation or sandboxing for untrusted STP/STEP files until the patch is deployed.

Recommended fix High confidence

Upgrade to AutoCAD and related products versions 2021.1.4, 2022.1.4, 2023.1.5, or 2024.1.3 (or later respective releases)

  1. Identify the exact version of affected Autodesk product currently installed
  2. Navigate to Autodesk Account or use the Autodesk Desktop App to check for updates
  3. Download the appropriate fixed version: 2021.1.4 (or later for 2021 line), 2022.1.4 (or later for 2022 line), 2023.1.5 (or later for 2023 line), or 2024.1.3 (or later for 2024 line)
  4. Ensure all users close the Autodesk application before initiating the upgrade
  5. Run the installer with administrative privileges
  6. Follow the on-screen installation prompts to complete the upgrade
  7. After installation, verify the installed version matches or exceeds the fixed version numbers
  8. Consider implementing additional mitigation: configure file execution policies to prompt before opening STP/STEP files from untrusted sources

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

Fix this in Autocad Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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