CVE-2024-23125
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 · uneditedA maliciously crafted SLDPRT file when parsed 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 confidenceA maliciously crafted SLDPRT file parsed through ODXSW_DLL.dll in Autodesk applications triggers a stack-based buffer overflow, potentially allowing an attacker to crash the application, read sensitive data, or execute arbitrary code in the context of the current process.
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>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1>= 2021, < 2021.1.4>= 2022, < 2022.1.4>= 2023, < 2023.1.5>= 2024, < 2024.1.3>= 2025, < 2025.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Autodesk applicationOpen Windows Control Panel > Programs and Features, or use 'Get-ItemProperty' PowerShell command: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like '*AutoCAD*' -or '*Civil*' -or '*Advance Steel*'}Affected if Any of the following products are installed: AutoCAD, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, Advance Steel, or AutoCAD Map 3D
-
Confirm exact version numberRun the application, go to Help > About, or check the installation directory for version information. In PowerShell: Get-ChildItem 'C:\Program Files\Autodesk' -Recurse -Filter 'acad.exe' | Select-Object FullName, VersionInfo | ForEach-Object { $_.VersionInfo } | Select-Object ProductName, ProductVersionAffected if The exact version cannot be determined or does not display in the expected format (e.g., 2021.x, 2022.x, etc.)
-
Compare version to affected rangesMatch your installed version against these ranges: 2021.0 to 2021.1.3 (vulnerable), 2022.0 to 2022.1.3 (vulnerable), 2023.0 to 2023.1.4 (vulnerable), 2024.0 to 2024.1.2 (vulnerable), 2025.0 to 2025.0.0 (vulnerable). If any part of the version string is lower than the minimum fixed version for that release line, the system is affected.Affected if Installed version falls within any of these ranges: >= 2021 but < 2021.1.4, >= 2022 but < 2022.1.4, >= 2023 but < 2023.1.5, >= 2024 but < 2024.1.3, >= 2025 but < 2025.0.1
-
Verify presence of vulnerable componentCheck if ODXSW_DLL.dll exists in the application installation directory. In PowerShell: Get-ChildItem 'C:\Program Files\Autodesk' -Recurse -Filter 'ODXSW_DLL.dll' -ErrorAction SilentlyContinue | Select-Object FullNameAffected if ODXSW_DLL.dll is found in the Autodesk application folder, indicating the parsing component is present
-
Check if SLDPRT file import is usedReview application usage patterns or logs to determine if users import or open SLDPRT (SolidWorks part) files. This file format is processed by the vulnerable ODXSW_DLL.dll component.Affected if Users open or import SLDPRT files within the affected Autodesk application
You are affected if an Autodesk product (AutoCAD, AutoCAD Electrical, Mechanical, MEP, Plant 3D, Civil 3D, Advance Steel, or Map 3D) is installed with a version within the ranges listed, and users process SLDPRT files with the ODXSW_DLL.dll component.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2021.1.42022.1.42023.1.5
Avoid opening untrusted or unverified SLDPRT files in affected Autodesk applications; implement input validation and sandboxing as compensating controls until vendor patch is available.
For 2021 releases: upgrade to 2021.1.4 or later | For 2022 releases: upgrade to 2022.1.4 or later | For 2023 releases: upgrade to 2023.1.5 or later | For 2024 releases: upgrade to 2024.1.3 or later
- Identify the exact installed version of the affected Autodesk product by opening the application and navigating to Help > About Autodesk [Product Name]
- Note the release year (2021, 2022, 2023, or 2024) and the current update version installed
- Close all Autodesk applications and any related processes
- Download the appropriate update from the Autodesk Account portal or the official Autodesk support website: https://www.autodesk.com/support
- For AutoCAD 2021: upgrade to version 2021.1.4 or later; For AutoCAD 2022: upgrade to version 2022.1.4 or later; For AutoCAD 2023: upgrade to version 2023.1.5 or later; For AutoCAD 2024: upgrade to version 2024.1.3 or later
- Run the downloaded installer with administrator privileges
- Follow the on-screen installation prompts to complete the update
- After installation, verify the updated version by checking Help > About Autodesk [Product Name]
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-23125 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23125 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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