Memory corruption via unvalidated DWF file parsing
Published Jan 25, 2022 · Updated Aug 4, 2024
Memory corruption in Autodesk Design Review 2018 allows remote attackers to trigger a read access violation using a crafted DWF or PCT file. The DWF parser fails to validate user-supplied data before memory access, producing the corruption condition. The target must visit a malicious page or open the file; code execution occurs in the current process only when chained with another vulnerability.
Summary
What happened
Memory corruption in Autodesk Design Review 2018 allows remote attackers to trigger a read access violation using a crafted DWF or PCT file. The DWF parser fails to validate user-supplied data before memory access, producing the corruption condition. The target must visit a malicious page or open the file; code execution occurs in the current process only when chained with another vulnerability.
The record
- CVE
- CVE-2021-40167
- Published
- Jan 25, 2022
- Updated
- Aug 4, 2024
- Vendor
- Autodesk
- Product
- Autodesk Design Review
- Classifications
- CWE-125, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 25, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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
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