Code execution via ODXSW_DLL.dll invalid write
Published Jun 25, 2024 · Updated Jan 22, 2026
Memory corruption in Autodesk AutoCAD-based products 2022 through 2025 allows attackers to execute code via crafted SLDASM or SLDPRT files. ODXSW_DLL.dll performs an invalid write while parsing attacker-controlled SolidWorks assembly or part data, corrupting process memory. A victim must open the file on an affected Windows installation; successful exploitation runs code in the current process.
Summary
What happened
Memory corruption in Autodesk AutoCAD-based products 2022 through 2025 allows attackers to execute code via crafted SLDASM or SLDPRT files. ODXSW_DLL.dll performs an invalid write while parsing attacker-controlled SolidWorks assembly or part data, corrupting process memory. A victim must open the file on an affected Windows installation; successful exploitation runs code in the current process.
The record
- CVE
- CVE-2024-23157
- Published
- Jun 25, 2024
- Updated
- Jan 22, 2026
- Vendor
- Autodesk
- Product
- AutoCAD Mechanical
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2024CVE publishedPublication date reported by the CVE source.
- Jan 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2022 <2022.1.5
- Affected versionversion=2023 <2023.1.6
- Affected versionversion=2024
- Affected versionversion=2024 <2024.1.5
- Affected versionversion=2025 <2025.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo