dbcve.org
AutocadApplication · Autodesk

CVE-2024-23140

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 3DM and MODEL file, when parsed in opennurbs.dll and atf_api.dll through Autodesk applications, can force an Out-of-Bound Read. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, 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

A file parsing vulnerability exists in Autodesk's opennurbs.dll and atf_api.dll libraries. When parsing maliciously crafted 3DM or MODEL files, the code performs an out-of-bounds memory read. This can allow an attacker to read sensitive memory contents, cause application crashes, or potentially achieve arbitrary code execution in the context of the current user process.

MitigationApply Autodesk security updates/patches to affected applications. Avoid opening 3DM or MODEL files from untrusted or 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 run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed Autodesk applications
    Affected if Any of the following products are installed: AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D
  2. Verify product version falls within affected range
    Check the installed version of the Autodesk product from Programs and Features or the application's About dialog. Compare against these vulnerable ranges: 2022 (any version < 2022.1.5), 2023 (any version < 2023.1.6), 2024 (any version < 2024.1.4), or 2025 (any version < 2025.1)
    Affected if The installed version is 2022.x before 2022.1.5, 2023.x before 2023.1.6, 2024.x before 2024.1.4, or 2025.x before 2025.1
  3. Confirm vulnerable DLL presence
    Search for opennurbs.dll or atf_api.dll in the product installation directory (typically C:\Program Files\Autodesk\<ProductName>\). Use command: dir /s C:\Program Files\Autodesk\opennurbs.dll
    Affected if opennurbs.dll or atf_api.dll exists in the Autodesk installation folder with a version predating the patched libraries
  4. Check for recent 3DM/MODEL file processing
    Review application logs, recent documents, or file access audit logs for .3dm or .model file openings. On Windows, check Recent folder: %APPDATA%\Autodesk\<Product>\Recent
    Affected if The application has recently opened or parsed 3DM or MODEL files, which triggers the vulnerable code path in opennurbs.dll or atf_api.dll

You are affected if you have any of the listed Autodesk products installed with version 2022.x < 2022.1.5, 2023.x < 2023.1.6, 2024.x < 2024.1.4, or 2025.x < 2025.1, and the vulnerable DLLs (opennurbs.dll or atf_api.dll) are present in the installation directory.

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 Autodesk security updates/patches to affected applications. Avoid opening 3DM or MODEL files from untrusted or unknown sources.

Recommended fix High confidence

2022.1.5 (or later) for 2022 product line; 2023.1.6 (or later) for 2023 product line; 2024.1.4 (or later) for 2024 product line; 2025.1 (or later) for 2025 product line

  1. 1. Identify the specific Autodesk product (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D) and version currently installed (2022, 2023, 2024, or 2025)
  2. 2. Close all running Autodesk applications on the system
  3. 3. Navigate to the Autodesk Support website at www.autodesk.com to download the appropriate security update
  4. 4. Download the fixed version: 2022.1.5 or later for 2022 products; 2023.1.6 or later for 2023 products; 2024.1.4 or later for 2024 products; 2025.1 or later for 2025 products
  5. 5. Run the installer and follow the on-screen instructions to apply the update
  6. 6. Restart the Autodesk application after installation completes
  7. 7. Verify the installed version matches the fixed release by checking Help > About in the application
Caveat Point releases typically include only security fixes with minimal compatibility impact; review Autodesk release notes for any API or feature changes

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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