Code execution via 3DM parser write violation
Published Jun 25, 2024 · Updated Jan 22, 2026
Memory corruption in Autodesk AutoCAD and affected toolsets allows attackers to execute code through a malicious 3DM file. opennurbs.dll and ASMkern229A.dll parse attacker-controlled 3DM data and perform an invalid write that corrupts process memory. Exploitation affects the listed Windows releases and requires a user to open the crafted file; resulting code runs in the current process.
Summary
What happened
Memory corruption in Autodesk AutoCAD and affected toolsets allows attackers to execute code through a malicious 3DM file. opennurbs.dll and ASMkern229A.dll parse attacker-controlled 3DM data and perform an invalid write that corrupts process memory. Exploitation affects the listed Windows releases and requires a user to open the crafted file; resulting code runs in the current process.
The record
- CVE
- CVE-2024-23156
- Published
- Jun 25, 2024
- Updated
- Jan 22, 2026
- Vendor
- Autodesk
- Product
- AutoCAD Mechanical
- Classifications
- CWE-787, CAPEC-100, 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 <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