Code execution via crafted DWFX heap overflow
Published Dec 17, 2024 · Updated Aug 26, 2025
Heap-based buffer overflow in Autodesk Navisworks 2025 before 2025.4 allows attackers to execute code through a crafted DWFX file. The DWFX parser writes beyond a heap buffer while processing attacker-controlled file content, but Autodesk has not identified the affected module or operation. Exploitation requires a user to open the file and can crash the application, expose process-accessible data, or run code in the current process.
Summary
What happened
Heap-based buffer overflow in Autodesk Navisworks 2025 before 2025.4 allows attackers to execute code through a crafted DWFX file. The DWFX parser writes beyond a heap buffer while processing attacker-controlled file content, but Autodesk has not identified the affected module or operation. Exploitation requires a user to open the file and can crash the application, expose process-accessible data, or run code in the current process.
The record
- CVE
- CVE-2024-12670
- Published
- Dec 17, 2024
- Updated
- Aug 26, 2025
- Vendor
- Autodesk
- Product
- Navisworks Simulate
- Classifications
- CWE-787, CWE-122, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 17, 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=2025 <2025.4
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