Code execution via PCT decoder bounds failure
Published Oct 21, 2022 · Updated May 7, 2025
Out-of-bounds memory access in DesignReview.exe in Autodesk Design Review 2018 and earlier allows remote attackers to execute code via PCT files. The PCT decoder fails to enforce buffer bounds and performs an out-of-bounds memory write while processing malformed file data. Exploitation requires a target to open the crafted file, and successful code runs in the context of the current DesignReview.exe process.
Summary
What happened
Out-of-bounds memory access in DesignReview.exe in Autodesk Design Review 2018 and earlier allows remote attackers to execute code via PCT files. The PCT decoder fails to enforce buffer bounds and performs an out-of-bounds memory write while processing malformed file data. Exploitation requires a target to open the crafted file, and successful code runs in the context of the current DesignReview.exe process.
The record
- CVE
- CVE-2022-42941
- Published
- Oct 21, 2022
- Updated
- May 7, 2025
- Vendor
- Autodesk
- Product
- Autodesk Design Review
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
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.
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