dbcve.org
AutocadApplication · Autodesk

CVE-2024-37003

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 DWG and SLDPRT file, when parsed in opennurbs.dll and ODXSW_DLL.dll through Autodesk applications, can be used to cause a Stack-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

Stack-based buffer overflow in Autodesk applications (opennurbs.dll and ODXSW_DLL.dll) when parsing maliciously crafted DWG and SLDPRT files. The overflow occurs during file parsing operations and can be exploited to cause application crashes, read sensitive memory contents, or achieve arbitrary code execution in the context of the current process.

MitigationUpdate Autodesk software to the latest patched version. Until patched, avoid opening DWG or SLDPRT files from untrusted or unknown sources, as the vulnerability is triggered upon file parsing.

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 applications
    Open Windows Control Panel > Programs and Features, or check Program Files for folders named AutoCAD, Civil 3D, or other Autodesk product names listed in the affected products
    Affected if Any of the following products are installed: AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D
  2. Determine the exact version of the installed Autodesk product
    In the application, go to Help > About to display the version and build number, or right-click the main executable (e.g., acad.exe) and select Properties > Details to view the Product Version
    Affected if The displayed version is any of: 2022 through 2022.1.4, 2023 through 2023.1.5, 2024 through 2024.1.3, or 2025 through 2025.0
  3. Confirm the file parsing component is present
    Check for the presence of opennurbs.dll or ODXSW_DLL.dll in the application installation directory (typically C:\Program Files\Autodesk\<ProductName>\)
    Affected if Either opennurbs.dll or ODXSW_DLL.dll exists in the product folder, indicating the vulnerable parsing component is available
  4. Verify parsing of DWG or SLDPRT files is possible
    Attempt to open any DWG or SLDPRT file in the installed product, or check the application's file open dialog for supported file types
    Affected if The product can open or attempts to parse DWG or SLDPRT files, which triggers the vulnerable code path

You are affected if an installed Autodesk product version falls within 2022 to 2022.1.4, 2023 to 2023.1.5, 2024 to 2024.1.3, or 2025 to 2025.0 and the application can parse DWG or SLDPRT 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

Update Autodesk software to the latest patched version. Until patched, avoid opening DWG or SLDPRT files from untrusted or unknown sources, as the vulnerability is triggered upon file parsing.

Recommended fix High confidence

Upgrade to the following fixed releases: Autocad/Civil 3d/vertical products 2022.1.5, 2023.1.6, 2024.1.4, or 2025.1 (depending on your product line year)

  1. Identify which Autodesk product (Autocad, Autocad Architecture, Autocad Electrical, Autocad Map 3d, Autocad Mechanical, Autocad Mep, Autocad Plant 3d, or Civil 3d) is installed and note the current version number
  2. For Autocad 2022 users: Upgrade to version 2022.1.5 or later
  3. For Autocad 2023 users: Upgrade to version 2023.1.6 or later
  4. For Autocad 2024 users: Upgrade to version 2024.1.4 or later
  5. For Autocad 2025 users: Upgrade to version 2025.1 or later
  6. Repeat the above version checks for all other affected vertical products (Architecture, Electrical, Map 3d, Mechanical, MEP, Plant 3d, Civil 3d) using the same version thresholds
  7. After upgrading, verify the installed version matches the fixed release
  8. Exercise caution when opening DWG or SLDPRT files from untrusted sources, as a mitigation in addition to patching
Caveat Review Autodesk's release notes for your target version for any compatibility or workflow changes before deploying in production environments

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
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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