Memory corruption via crafted DWF or PCT files
Published Oct 21, 2022 · Updated May 7, 2025
Memory corruption in Autodesk Design Review 2018, 2017, 2013, 2012, and 2011 allows attackers to corrupt memory via crafted DWF or PCT files. DesignReview.exe performs an invalid write access while consuming the crafted file, corrupting memory in the current process. Opening the file or visiting a malicious page requires user interaction; code execution requires chaining the flaw with other vulnerabilities.
Summary
What happened
Memory corruption in Autodesk Design Review 2018, 2017, 2013, 2012, and 2011 allows attackers to corrupt memory via crafted DWF or PCT files. DesignReview.exe performs an invalid write access while consuming the crafted file, corrupting memory in the current process. Opening the file or visiting a malicious page requires user interaction; code execution requires chaining the flaw with other vulnerabilities.
The record
- CVE
- CVE-2022-42933
- Published
- Oct 21, 2022
- Updated
- May 7, 2025
- Vendor
- Autodesk
- Product
- Autodesk Design Review
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 21, 2022CVE publishedPublication date reported by the CVE source.
- May 7, 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=2018, 2017, 2013, 2012, 2011
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.
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