dbcve.org
AutocadApplication · Autodesk

CVE-2024-23129

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 MODEL 3DM, STP, or SLDASM file, when in opennurbs.dll parsed through Autodesk applications, can lead to a memory corruption vulnerability by write access violation. This vulnerability, in conjunction with other vulnerabilities, can lead to code execution 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 memory corruption vulnerability in opennurbs.dll allows write access violation when parsing maliciously crafted MODEL 3DM, STP, or SLDASM files. This can lead to code execution in the current process context when chained with other vulnerabilities.

MitigationApply vendor patches for opennurbs.dll when available; avoid opening untrusted 3DM, STP, or SLDASM files until patches are 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 installed Autodesk product
    Check Add/Remove Programs or look for AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel in the program directory (typically C:\Program Files\Autodesk\)
    Affected if One of the listed affected products is installed
  2. Determine product version
    Open the application, go to Help > About Autodesk [Product], or right-click the executable in Program Files > Properties > Details to see the version number
    Affected if Version falls within any of these ranges: 2021 (before 2021.1.4), 2022 (before 2022.1.4), 2023 (before 2023.1.5), 2024 (before 2024.1.3), or 2025 (before 2025.0.1)
  3. Locate opennurbs.dll
    Search for opennurbs.dll in the application bin folder (typically C:\Program Files\Autodesk\[Product]\) or use PowerShell: Get-ChildItem -Path 'C:\Program Files\Autodesk' -Recurse -Filter 'opennurbs.dll'
    Affected if The DLL exists in the Autodesk product installation directory
  4. Check DLL version
    Right-click opennurbs.dll > Properties > Details, or run: (Get-Item 'path\to\opennurbs.dll').VersionInfo | Format-List *
    Affected if DLL version is lower than the patched version corresponding to the product year (the patch updates this DLL)
  5. Assess file handling exposure
    Determine if the system can process 3DM, STP, or SLDASM files. Check file associations, recent files, or look for these extensions in the user's Documents or common project folders
    Affected if Users routinely open or import 3DM, STP, or SLDASM files from external sources

You are affected if you have any of the listed Autodesk products installed with a version below the patched release (2021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, or 2025.0.1) AND users process 3DM, STP, or SLDASM 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 2021.1.4 / 2022.1.4 / 2023.1.5 or later
Fixed in 2021.1.42022.1.42023.1.5
Interim mitigation

Apply vendor patches for opennurbs.dll when available; avoid opening untrusted 3DM, STP, or SLDASM files until patches are deployed.

Recommended fix High confidence

Upgrade to AutoCAD/related product version 2024.1.3 (or the corresponding fixed version for your product line: 2021.1.4, 2022.1.4, 2023.1.5)

  1. Identify the specific Autodesk product and version currently installed (e.g., AutoCAD 2023, Civil 3D 2022, etc.)
  2. Navigate to the Autodesk Account or the product's support page to download the update
  3. Download and install the appropriate update based on your product version: For 2021.x products, install version 2021.1.4 or later; For 2022.x products, install version 2022.1.4 or later; For 2023.x products, install version 2023.1.5 or later; For 2024.x products, install version 2024.1.3 or later
  4. Restart the application after installation
  5. Verify the installed version matches or exceeds the fixed version for your product line
Caveat Standard Autodesk update best practices apply - verify custom scripts and add-ins compatibility in a test environment before deploying widely

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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