dbcve.org
AutocadApplication · Autodesk

CVE-2024-23152

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 through Autodesk applications, can force an Out-of-Bounds 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 crafted 3DM file triggers an out-of-bounds read vulnerability in the opennurbs.dll library when parsed by Autodesk applications. This memory safety flaw can be leveraged to crash the application, expose sensitive process memory, or achieve arbitrary code execution in the current process context.

MitigationApply the vendor-supplied security patch from Autodesk for the affected products. Avoid opening untrusted or originated-from-unknown-sources 3DM files until the patch is applied.

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, go to Help > About Autodesk [Product Name], or run the application and check the title bar/splash screen for the product name and version
    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 the exact version number
    In the application, use the command line to type 'VER' or 'ABOUT' to display the full version and build number
    Affected if The displayed version falls within any of these ranges: >=2022 but <2022.1.5; >=2023 but <2023.1.6; >=2024 but <2024.1.5; >=2025 but <2025.1
  3. Verify opennurbs.dll is present
    Search for opennurbs.dll in the application installation directory (typically C:\Program Files\Autodesk\[ProductName]\[Version]\) or check the file properties of the library loaded in the process
    Affected if The DLL exists in the application directory (its presence indicates the vulnerable component is available for 3DM file parsing)
  4. Confirm 3DM file handling capability
    Attempt to open a 3DM file in the application, or check File > Open dialog for .3dm file type support
    Affected if 3DM files can be opened or imported (the vulnerability triggers during parsing of these files)

You are affected if you have any of the listed Autodesk products installed with a version number that is less than 2022.1.5, 2023.1.6, 2024.1.5, or 2025.1 respectively.

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 vendor-supplied security patch from Autodesk for the affected products. Avoid opening untrusted or originated-from-unknown-sources 3DM files until the patch is applied.

Recommended fix High confidence

Upgrade to: AutoCAD 2022.1.5+, AutoCAD 2023.1.6+, AutoCAD 2024.1.5+, AutoCAD 2025.1+ (and corresponding versions for Architecture, Electrical, Map 3D, Mechanical, MEP, Plant 3D, and Civil 3D)

  1. 1. Identify the exact version of the affected Autodesk product installed (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D)
  2. 2. Navigate to the official Autodesk support website or use the application's built-in update checker
  3. 3. Download the appropriate security update for your product version: For 2022.x versions, upgrade to 2022.1.5 or later; For 2023.x versions, upgrade to 2023.1.6 or later; For 2024.x versions, upgrade to 2024.1.5 or later; For 2025.x versions, upgrade to 2025.1 or later
  4. 4. Ensure all running Autodesk applications are closed before applying the update
  5. 5. Run the installer with administrative privileges and follow the on-screen prompts
  6. 6. After installation, verify the new version by checking Help > About in the application
  7. 7. Apply the same update to any other affected products running on the same system
Caveat Review Autodesk's release notes for the new version to check for any workflow changes or deprecated features that may affect existing projects or scripts

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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