dbcve.org
AutocadApplication · Autodesk

CVE-2024-23130

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 SLDASM or SLDPRT file, when parsed in ODXSW_DLL.dll 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 exists in ODXSW_DLL.dll within Autodesk applications when parsing maliciously crafted SLDASM or SLDPRT files (SolidWorks assembly and part file formats). The vulnerability manifests as a write access violation that can be leveraged alongside other vulnerabilities to achieve code execution in the context of the current process.

MitigationAvoid opening untrusted or unverified SLDASM and SLDPRT files until Autodesk releases an official patch for ODXSW_DLL.dll. Apply vendor security updates promptly when available.

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
    Open Windows Control Panel > Programs and Features, or use 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName' in PowerShell to list installed software containing 'Autodesk'
    Affected if Any of these products are installed: AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel
  2. Check product version
    Right-click the application shortcut > Properties > General tab, or check the registry under HKLM\SOFTWARE\Autodesk\[ProductName] for the Version value
    Affected if Version is 2021.x where x < 1.4, 2022.x where x < 1.4, 2023.x where x < 1.5, 2024.x where x < 1.3, or 2025.x where x < 1 (e.g., 2025.0.0)
  3. Locate ODXSW_DLL.dll
    Search for ODXSW_DLL.dll in the application installation directory (typically C:\Program Files\Autodesk\[ProductName]\) using Get-ChildItem -Recurse or File Explorer search
    Affected if The DLL file exists in the Autodesk application folder, indicating the vulnerable component is present
  4. Check for recent file operations
    Review recent file access logs or the application's recent files list for any opened .SLDASM or .SLDPRT files from untrusted sources
    Affected if A user has recently opened a SLDASM or SLDPRT file from an untrusted or unknown source

If an affected Autodesk product version (2021 through 2025, below the patched thresholds) with ODXSW_DLL.dll present has been used to open SLDASM/SLDPRT files, the environment is likely vulnerable to CVE-2024-23130.

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

Avoid opening untrusted or unverified SLDASM and SLDPRT files until Autodesk releases an official patch for ODXSW_DLL.dll. Apply vendor security updates promptly when available.

Recommended fix High confidence

AutoCAD 2021.1.4, 2022.1.4, 2023.1.5, and 2024.1.3 (or later) depending on product line

  1. Identify the specific Autodesk product and version currently installed (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel)
  2. For AutoCAD 2021 users: Upgrade to version 2021.1.4 or later
  3. For AutoCAD 2022 users: Upgrade to version 2022.1.4 or later
  4. For AutoCAD 2023 users: Upgrade to version 2023.1.5 or later
  5. For AutoCAD 2024 users: Upgrade to version 2024.1.3 or later
  6. Apply the same version upgrades to the corresponding vertical products (Architecture, Electrical, Mechanical, MEP, Plant 3D, Civil 3D, Advance Steel)
  7. Verify the installation by checking the updated version number in the application's About dialog
  8. Restart the application after updating

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-23130 — 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-23130 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