dbcve.org
AutocadApplication · Autodesk

CVE-2024-23154

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 SLDPRT file, when parsed in ODXSW_DLL.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 · moderate confidence

A heap-based buffer overflow vulnerability exists in ODXSW_DLL.dll when parsing maliciously crafted SLDPRT (SolidWorks part) files through Autodesk applications. The overflow allows an attacker to potentially crash the application, read sensitive memory contents, or execute arbitrary code within the current process context.

MitigationApply the vendor patch from Autodesk immediately, and implement file parsing restrictions or sandboxing for untrusted SLDPRT files until the update is deployed.

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 and version
    Open the Autodesk application, go to Help > About Autodesk [Product], or check the installation folder for version info in the program name or manifest file. Use 'Add or Remove Programs' in Windows Control Panel to view installed versions.
    Affected if The installed version matches one of the affected version ranges (2022 < 2022.1.5, 2023 < 2023.1.6, 2024 < 2024.1.5, or 2025 < 2025.1)
  2. Locate ODXSW_DLL.dll in the installation directory
    Search for ODXSW_DLL.dll in the Autodesk application installation folder, typically found in the bin directory under the product folder. Use Windows Explorer or the 'where' command in Command Prompt: where /r [install drive]:\Program Files\Autodesk ODXSW_DLL.dll
    Affected if The DLL file exists, indicating the vulnerable component is present on the system
  3. Verify SLDPRT import capability is available
    Check if the application has import functionality for SLDPRT files. In AutoCAD, try to insert or import a .sldPRT file, or check File > Open and look for SLDPRT as a selectable file type in the dialog.
    Affected if The application can import or open SLDPRT files, meaning the vulnerable parsing code path could be triggered
  4. Compare installed version against affected ranges
    Document the exact version number found in step 1 and compare it against the affected ranges: for 2022 versions, any build below 2022.1.5; for 2023, below 2023.1.6; for 2024, below 2024.1.5; for 2025, below 2025.1. Check the build number in the About dialog or program metadata.
    Affected if The installed version falls within any of the affected ranges (e.g., 2022.0.0 through 2022.1.4, 2023.0.0 through 2023.1.5, etc.)

You are affected if you have any of the listed Autodesk products installed with a version that falls within the affected ranges and the ODXSW_DLL.dll component is present, allowing SLDPRT file parsing to trigger the vulnerability.

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 the vendor patch from Autodesk immediately, and implement file parsing restrictions or sandboxing for untrusted SLDPRT files until the update is deployed.

Recommended fix High confidence

Upgrade to AutoCAD/Civil 3D/etc. version 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. 1. Identify the exact version of the affected Autodesk product installed (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, or Civil 3D)
  2. 2. Open the Autodesk product and navigate to Help > About Autodesk Product to view the version number
  3. 3. Close all Autodesk applications completely
  4. 4. Download the appropriate fixed version from the Autodesk Account portal or official Autodesk support site: For 2022.x versions, upgrade to 2022.1.5 or later; For 2023.x versions, upgrade to 2023.1.6 or later; For 2024.x versions, upgrade to 2024.1.5 or later; For 2025.x versions, upgrade to 2025.1 or later
  5. 5. Run the installer with administrator privileges
  6. 6. Follow the on-screen installation prompts
  7. 7. After installation completes, verify the new version by checking Help > About Autodesk Product
  8. 8. Avoid opening untrusted SLDPRT files in the future or use Autodesk's Trusted Paths feature to restrict file execution locations
Caveat Review Autodesk's compatibility documentation for your specific version upgrade as newer releases may have drawing format or API compatibility changes with older versions

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

Fix this in Autocad Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing10.0 h
  • Review / QA3.0 h
23.0 hours of engineering $3,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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