dbcve.org
AutocadApplication · Autodesk

CVE-2024-36999

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 Write. A malicious actor can leverage this vulnerability to cause a crash, write 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

An out-of-bounds write vulnerability exists in opennurbs.dll when parsing maliciously crafted 3DM files in Autodesk applications. The vulnerability allows a local attacker to execute arbitrary code or cause a denial of service by tricking a user into opening a specially crafted 3DM file.

MitigationApply vendor patches from Autodesk for affected products. Until patches are available, avoid opening 3DM files from untrusted sources and consider using application sandboxing or disabling file preview features.

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
    Check installed programs in Windows Settings > Apps > Installed Apps, or look for Autodesk application folders in C:\Program Files\Autodesk or C:\Program Files (x86)\Autodesk
    Affected if Any of these products are present: Autocad, Autocad Architecture, Autocad Electrical, Autocad Map 3d, Autocad Mechanical, Autocad Mep, Autocad Plant 3d, or Civil 3d
  2. Determine product version
    Open the installed Autodesk application, go to Help > About, or right-click the executable in Program Files and view Properties > Details for the File Version
    Affected if Version matches any of these ranges: 2022.x before 2022.1.5; 2023.x before 2023.1.6; 2024.x before 2024.1.5; 2025.x before 2025.1
  3. Confirm opennurbs.dll is present
    Search for opennurbs.dll in the application installation directory (e.g., C:\Program Files\Autodesk\AutoCAD 2024\)
    Affected if opennurbs.dll exists in the Autodesk product folder, indicating the vulnerable component is installed
  4. Check if 3DM file association exists
    Look for .3dm file type associations in Windows Registry under HKEY_CLASSES_ROOT\.3dm or check if the application can open 3DM files
    Affected if The product has .3dm file associations or can open 3DM files, meaning the attack surface is present

If any of the listed Autodesk products are installed with versions in the ranges 2022 < 2022.1.5, 2023 < 2023.1.6, 2024 < 2024.1.5, or 2025 < 2025.1, the environment is vulnerable when 3DM file handling is available.

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 vendor patches from Autodesk for affected products. Until patches are available, avoid opening 3DM files from untrusted sources and consider using application sandboxing or disabling file preview features.

Recommended fix High confidence

Upgrade to 2022.1.5 (or later), 2023.1.6 (or later), 2024.1.5 (or later), or 2025.1 (or later) depending on your product line

  1. Identify the specific Autodesk product and version currently installed (e.g., AutoCAD 2023, Civil 3D 2024, etc.)
  2. Navigate to the Autodesk Account or product's Help section to download the latest update
  3. For AutoCAD 2022: upgrade to version 2022.1.5 or later
  4. For AutoCAD 2023: upgrade to version 2023.1.6 or later
  5. For AutoCAD 2024: upgrade to version 2024.1.5 or later
  6. For AutoCAD 2025: upgrade to version 2025.1 or later
  7. Alternatively, apply the same version thresholds to related products (AutoCAD Architecture, Electrical, Map 3D, Mechanical, MEP, Plant 3D, Civil 3D)
  8. After upgrading, verify the version by typing VER or ABOUT in the product command line
Caveat Standard Autodesk update; review release notes for new features but no expected breaking changes for typical workflows

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,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 $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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