Code execution via unvalidated FBX file parsing
Published Apr 19, 2021 · Updated Aug 3, 2024
Memory corruption in Autodesk FBX Review 1.5.0 and earlier allows remote attackers to execute code through a crafted FBX file. The FBX parser fails to validate user-supplied data before processing it, producing a memory-corruption condition within the current process. Exploitation requires a user to visit a malicious page or open the crafted file, and resulting code runs with the process's privileges.
Summary
What happened
Memory corruption in Autodesk FBX Review 1.5.0 and earlier allows remote attackers to execute code through a crafted FBX file. The FBX parser fails to validate user-supplied data before processing it, producing a memory-corruption condition within the current process. Exploitation requires a user to visit a malicious page or open the crafted file, and resulting code runs with the process's privileges.
The record
- CVE
- CVE-2021-27028
- Published
- Apr 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Autodesk
- Product
- FBX Review
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 19, 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=1.4.1.0
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