Code execution via out-of-bounds 3DM parser write
Published Feb 22, 2024 · Updated Aug 28, 2025
Out-of-bounds write in Autodesk AutoCAD allows attackers to execute code in the current process when a user opens a crafted 3DM file. The opennurbs.dll parser fails to validate user-supplied 3DM data before writing past the end of an allocated buffer. Exploitation requires user interaction; failed exploitation can crash the application or corrupt data.
Summary
What happened
Out-of-bounds write in Autodesk AutoCAD allows attackers to execute code in the current process when a user opens a crafted 3DM file. The opennurbs.dll parser fails to validate user-supplied 3DM data before writing past the end of an allocated buffer. Exploitation requires user interaction; failed exploitation can crash the application or corrupt data.
The record
- CVE
- CVE-2024-23122
- Published
- Feb 22, 2024
- Updated
- Aug 28, 2025
- Vendor
- Autodesk
- Product
- AutoCAD Mechanical
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 2024CVE publishedPublication date reported by the CVE source.
- Aug 28, 2025Record 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=2021 <2021.1.4
- Affected versionversion=2022 <2022.1.4
- Affected versionversion=2023 <2023.1.5
- Affected versionversion=2024 <2024.1.3
- Affected versionversion=2025 <2025.0.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