dbcve.org
AutocadApplication · Autodesk

CVE-2024-23156

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 file, when parsed in opennurbs.dll and ASMkern229A.dll through Autodesk applications, can lead to a memory corruption vulnerability by write access violation. This vulnerability, along with other vulnerabilities, can 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 · high confidence

A memory corruption vulnerability exists in Autodesk applications' 3DM file parsing libraries (opennurbs.dll and ASMkern229A.dll). When parsing a maliciously crafted 3DM file, a write access violation occurs due to improper bounds checking during parsing, potentially allowing an attacker to achieve code execution in the current process context.

MitigationApply the Autodesk security update for this vulnerability. Until patches are available, avoid opening untrusted 3DM files and consider running Autodesk applications with reduced privileges to limit impact of potential exploitation.

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 installed Autodesk product
    Open the application and check Help > About Autodesk [Product Name], or check Add/Remove Programs for the installed Autodesk application name (e.g., AutoCAD 2024, AutoCAD Architecture 2024, Civil 3D 2024)
    Affected if The product is one of AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D
  2. Determine installed version number
    In the application, type 'VER' at the command line and press Enter, or check Help > About to display the version and build number
    Affected if The displayed version falls within any of these ranges: 2022 to 2022.1.4, 2023 to 2023.1.5, 2024 to 2024.1.4, or 2025 to 2025.0 (meaning any version before the fixed releases)
  3. Locate vulnerable DLL files
    Search for opennurbs.dll and ASMkern229A.dll in the application installation directory (commonly C:\Program Files\Autodesk\[ProductName]\[Version])
    Affected if Both DLL files exist in the application folder, indicating the vulnerable parsing libraries are present
  4. Verify 3DM file handling capability
    Check if the application can import or open .3DM files by attempting to insert a 3DM file or checking file association settings
    Affected if The application has 3DM import functionality enabled and can process 3DM files, which is the attack vector for this vulnerability

You are affected if you have any of the listed AutoCAD variants or Civil 3D installed with version 2022.x through 2024.x (before .1.5/.1.5/.1.4 respectively) or version 2025.x before 2025.1, and the application can open 3DM 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 2022.1.5 / 2023.1.6 / 2024.1.5 or later
Fixed in 2022.1.52023.1.62024.1.5
Interim mitigation

Apply the Autodesk security update for this vulnerability. Until patches are available, avoid opening untrusted 3DM files and consider running Autodesk applications with reduced privileges to limit impact of potential exploitation.

Recommended fix High confidence

Upgrade to AutoCAD 2022.1.5 / 2023.1.6 / 2024.1.5 / 2025.1 or later (or the latest available version of your product line)

  1. 1. Identify the installed Autodesk product and version (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D)
  2. 2. Close any running Autodesk application
  3. 3. Download the appropriate fixed version from the official Autodesk website or through your Autodesk Account/Desktop App
  4. 4. For AutoCAD 2022: Upgrade to version 2022.1.5 or later
  5. 5. For AutoCAD 2023: Upgrade to version 2023.1.6 or later
  6. 6. For AutoCAD 2024: Upgrade to version 2024.1.5 or later
  7. 7. For AutoCAD 2025: Upgrade to version 2025.1 or later
  8. 8. Install the update following Autodesk's standard installation procedure
Caveat Standard Autodesk update considerations apply - verify that custom scripts, plug-ins, andworkspaces are compatible with the new version before deploying broadly

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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