Code execution via crafted DWG parsing
Published Oct 29, 2024 · Updated Aug 26, 2025
Out-of-bounds write in Autodesk AutoCAD and affected desktop products allows attackers to execute code through a crafted DWG file. The DWG parser writes beyond an allocated memory boundary while processing malformed file data; Autodesk has not identified the responsible module or routine. A user must open or otherwise parse the file, after which the current process can crash, corrupt data, or execute attacker-controlled code.
Summary
What happened
Out-of-bounds write in Autodesk AutoCAD and affected desktop products allows attackers to execute code through a crafted DWG file. The DWG parser writes beyond an allocated memory boundary while processing malformed file data; Autodesk has not identified the responsible module or routine. A user must open or otherwise parse the file, after which the current process can crash, corrupt data, or execute attacker-controlled code.
The record
- CVE
- CVE-2024-7991
- Published
- Oct 29, 2024
- Updated
- Aug 26, 2025
- Vendor
- Autodesk
- Product
- AutoCAD Mechanical
- Classifications
- CWE-787, T1203, T1204.002, T1566.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 26, 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=2022 <2022.1.6
- Affected versionversion=2023 <2023.1.7
- Affected versionversion=2024 <2024.1.7
- Affected versionversion=2025 <2025.1.1
What conditions does exploitation require?
What is affected?
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