dbcve.org
AutocadApplication · Autodesk

CVE-2024-23137

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 STP or SLDPRT file, when parsed in ODXSW_DLL.dll through Autodesk applications, can be used to uninitialized variables. This vulnerability, along with other vulnerabilities, can lead to code execution in 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 · moderate confidence

A vulnerability in ODXSW_DLL.dll allows parsing of maliciously crafted STP or SLDPRT files to trigger use of uninitialized variables, which can be leveraged for code execution in the context of the Autodesk application process.

MitigationApply vendor patches for affected Autodesk applications; avoid opening untrusted STP or SLDPRT files from unknown sources until patches are 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:>= 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 and version
    Open Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\[ProductName] (e.g., AutoCAD, Civil3D). Locate the 'Version' or 'Release' key to determine the installed version (e.g., 2021, 2022, 2023, 2024, 2025).
    Affected if The installed version is 2021, 2022, 2023, 2024, or 2025 and is below the patched versions (2021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, 2025.0.1)
  2. Locate ODXSW_DLL.dll on the system
    Search for ODXSW_DLL.dll in the Autodesk installation directory using Windows Explorer or PowerShell: Get-ChildItem -Path 'C:\Program Files\Autodesk' -Recurse -Filter 'ODXSW_DLL.dll' -ErrorAction SilentlyContinue
    Affected if The DLL exists in the product directory and the parent product version falls within the affected ranges
  3. Verify file handling is enabled
    Check if the application can open STP or SLDPRT files by examining file association settings in Windows Registry under HKEY_CLASSES_ROOT\.stp and HKEY_CLASSES_ROOT\.sldprt, or by attempting to open a sample file in the Autodesk application
    Affected if STP or SLDPRT file handling is active and the product version is within the affected ranges

The environment is affected if an Autodesk product version is 2021 through 2025 and is below the patched releases (2021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, 2025.0.1), with ODXSW_DLL.dll present and file parsing enabled.

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 affected Autodesk applications; avoid opening untrusted STP or SLDPRT files from unknown sources until patches are applied.

Recommended fix High confidence

2021.1.4 (for 2021.x), 2022.1.4 (for 2022.x), 2023.1.5 (for 2023.x), or 2024.1.3 (for 2024.x) depending on product line

  1. Identify the specific Autodesk product (e.g., AutoCAD, AutoCAD Architecture, Civil 3D, etc.) and version (2021, 2022, 2023, or 2024) currently installed
  2. Open the Autodesk product and navigate to the Help menu or account settings to check the current version number
  3. For AutoCAD 2021.x: Upgrade to version 2021.1.4
  4. For AutoCAD 2022.x: Upgrade to version 2022.1.4
  5. For AutoCAD 2023.x: Upgrade to version 2023.1.5
  6. For AutoCAD 2024.x: Upgrade to version 2024.1.3
  7. For other affected products (AutoCAD Architecture, Electrical, Mechanical, MEP, Plant 3D, Civil 3D, Advance Steel): Apply the corresponding version-specific patch (2021.1.4, 2022.1.4, 2023.1.5, or 2024.1.3)
  8. Restart the application after 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
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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