Code execution via PDF parser type confusion
Published Jul 9, 2021 · Updated Aug 3, 2024
Type confusion in Autodesk Design Review 2011, 2012, 2013, 2017, and 2018 allows attackers to execute code via a crafted PDF file. The PDF parser fails to validate untrusted data before treating an object as an incompatible type, causing type confusion in the current process. Exploitation requires the target to open the file or visit a malicious page, and resulting code runs with the current process's privileges.
Summary
What happened
Type confusion in Autodesk Design Review 2011, 2012, 2013, 2017, and 2018 allows attackers to execute code via a crafted PDF file. The PDF parser fails to validate untrusted data before treating an object as an incompatible type, causing type confusion in the current process. Exploitation requires the target to open the file or visit a malicious page, and resulting code runs with the current process's privileges.
The record
- CVE
- CVE-2021-27038
- Published
- Jul 9, 2021
- Updated
- Aug 3, 2024
- Vendor
- Autodesk
- Product
- Autodesk Design Review
- Classifications
- CWE-843, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 9, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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, 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