dbcve.org
AutocadApplication · Autodesk

CVE-2024-23155

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 MODEL file, when parsed in atf_asm_interface.dll through Autodesk applications, can be used to cause a Heap-based Buffer Overflow. A malicious actor can leverage this vulnerability to cause a crash 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

Heap-based buffer overflow vulnerability in atf_asm_interface.dll when Autodesk applications parse maliciously crafted MODEL files, allowing attackers to cause crashes or execute arbitrary code in the current process context.

MitigationAvoid opening untrusted or unknown MODEL files until vendor patches are applied; update Autodesk applications to the latest patched versions.

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.5>= 2025, < 2025.1
Autocad ArchitectureApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.1
Autocad ElectricalApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.1
Autocad Map 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.1
Autocad MechanicalApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.1
Autocad MepApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.1
Autocad Plant 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 2025, < 2025.1
Civil 3dApplication
Affected:>= 2022, < 2022.1.5>= 2023, < 2023.1.6>= 2024, < 2024.1.5>= 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 the installed Autodesk application and version
    Open the Autodesk application, then go to Help > About (or use the command bar to type ABOUT) to display the version and build number. Alternatively, check the Windows Programs and Features list (appwiz.cpl) for the installed version.
    Affected if The application is one of: AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D, with a version that falls within 2022 < 2022.1.5, 2023 < 2023.1.6, 2024 < 2024.1.5, or 2025 < 2025.1.
  2. Locate the atf_asm_interface.dll file
    Search for atf_asm_interface.dll within the application installation directory (typically C:\Program Files\Autodesk\<ProductName>\) or subdirectories such as Support,bin, or PlugIns.
    Affected if The DLL is present in the application directory, indicating the vulnerable component is installed.
  3. Determine if the application is configured to handle MODEL files
    Check the Windows Default Programs settings, or right-click a .model file in File Explorer, select Properties, and view which application is listed under 'Opens with'. Alternatively, within the Autodesk application, check the File > Open dialog to see if .model files are listed as a supported format.
    Affected if The Autodesk application is set as the default handler for .model files, meaning it will parse files that could exploit this vulnerability.
  4. Compare installed version to the affected version ranges
    Note the exact version string (for example: 2022.1.4, 2023.1.5, 2024.1.4, or 2025.0) from step 1 and compare it to the vulnerable ranges: any version less than 2022.1.5, 2023.1.6, 2024.1.5, or 2025.1 is affected.
    Affected if The installed version is lower than the first safe version in any of the four major release branches (2022.1.5, 2023.1.6, 2024.1.5, or 2025.1).

You are affected if you have any of the listed Autodesk products installed with a version that falls within the vulnerable ranges and the atf_asm_interface.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 2022.1.5 / 2023.1.6 / 2024.1.5 or later
Fixed in 2022.1.52023.1.62024.1.5
Interim mitigation

Avoid opening untrusted or unknown MODEL files until vendor patches are applied; update Autodesk applications to the latest patched versions.

Recommended fix High confidence

Minimum fixed versions: AutoCAD/Civil 3D/Architecture/Electrical/Map3D/Mechanical/MEP/Plant3D 2022.1.5, 2023.1.6, 2024.1.5, or 2025.1 (or later respective releases)

  1. Identify the exact installed version of the affected Autodesk product (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D)
  2. Navigate to the Autodesk Account or official Autodesk support website at www.autodesk.com
  3. Locate the updates or downloads section for your specific product
  4. Download the appropriate update based on your product version: For 2022 products, download version 2022.1.5 or later; For 2023 products, download version 2023.1.6 or later; For 2024 products, download version 2024.1.5 or later; For 2025 products, download version 2025.1 or later
  5. Close all running instances of the Autodesk application
  6. Run the installer or update package with administrative privileges
  7. Follow the on-screen installation prompts to complete the update
  8. Restart the application and verify the update was successful by checking the About screen for the new version number
Caveat Standard Autodesk update considerations apply - ensure project files are backed up before updating; some older custom scripts or third-party plugins may require verification of compatibility with the new version

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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