dbcve.org
AutocadApplication · Autodesk

CVE-2024-37001

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 be used to cause a Heap-based Overflow. 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 heap-based buffer overflow vulnerability exists in opennurbs.dll when parsing maliciously crafted 3DM files. The overflow occurs during file parsing operations and can allow an attacker to corrupt heap memory, potentially leading to arbitrary code execution in the context of the running application.

MitigationApply vendor-supplied patches for affected Autodesk applications when available. Until a patch is released, avoid opening 3DM files from untrusted 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 use PowerShell: Get-WmiObject -Class Win32_Product | Select-Object Name, Version
    Affected if Any of these products are listed: Autocad, Autocad Architecture, Autocad Electrical, Autocad Map 3d, Autocad Mechanical, Autocad Mep, Autocad Plant 3d, or Civil 3d
  2. Verify product version against affected ranges
    Note the installed version from the previous step and compare it to: 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 falls within any of these ranges and matches the product names listed in the CVE
  3. Locate opennurbs.dll file
    Search for opennurbs.dll in the product installation directory, typically found in the program files folder under the Autodesk product folder, or use: Get-ChildItem -Path "C:\Program Files\Autodesk" -Recurse -Filter "opennurbs.dll" -ErrorAction SilentlyContinue
    Affected if opennurbs.dll exists in an Autodesk product installation folder, indicating the vulnerable component is present
  4. Check if 3DM file parsing is used
    Determine if users routinely import or open .3dm files within the Autodesk application. This is the attack vector for this vulnerability.
    Affected if The application is used to open or import 3DM files from any source, which triggers the vulnerable parsing code path in opennurbs.dll

Your environment is affected if you have any of the listed Autodesk products installed with a version matching the affected ranges and you use the application to 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.4 or later
Fixed in 2022.1.52023.1.62024.1.4
Interim mitigation

Apply vendor-supplied patches for affected Autodesk applications when available. Until a patch is released, avoid opening 3DM files from untrusted sources.

Recommended fix High confidence

AutoCAD 2022.1.5+, 2023.1.6+, 2024.1.4+, 2025.1+ (and corresponding versions for AutoCAD Architecture, Electrical, Map 3d, Mechanical, MEP, Plant 3d, and Civil 3d)

  1. 1. Identify the exact installed version of the affected Autodesk product (Autocad, Autocad Architecture, Autocad Electrical, Autocad Map 3d, Autocad Mechanical, Autocad Mep, Autocad Plant 3d, or Civil 3d).
  2. 2. Determine the product year (2022, 2023, 2024, or 2025).
  3. 3. For AutoCAD 2022 users: Upgrade to version 2022.1.5 or later.
  4. 4. For AutoCAD 2023 users: Upgrade to version 2023.1.6 or later.
  5. 5. For AutoCAD 2024 users: Upgrade to version 2024.1.4 or later.
  6. 6. For AutoCAD 2025 users: Upgrade to version 2025.1 or later.
  7. 7. Apply the same version thresholds to any specialized AutoCAD variants (Architecture, Electrical, Map 3d, Mechanical, MEP, Plant 3d) and Civil 3d.
  8. 8. Download the updates from the official Autodesk website (www.autodesk.com) or use the Autodesk Access application to apply updates.
Caveat Review Autodesk's release notes for your specific product version for any compatibility notes or known issues before upgrading

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation40.0 h
  • Testing16.0 h
  • Review / QA8.0 h
68.0 hours of engineering $11,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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