Code execution via unvalidated object use
Published Apr 19, 2021 · Updated Aug 3, 2024
Use-after-free in Autodesk FBX Review 1.4.1.0 and 1.5.0 allows remote attackers to execute code through a malicious FBX file. During FBX parsing, the application performs operations on an object without first validating that the object still exists, dereferencing freed memory. Exploitation requires the target to visit a malicious page or open the file and runs code in the context of the current process.
Summary
What happened
Use-after-free in Autodesk FBX Review 1.4.1.0 and 1.5.0 allows remote attackers to execute code through a malicious FBX file. During FBX parsing, the application performs operations on an object without first validating that the object still exists, dereferencing freed memory. Exploitation requires the target to visit a malicious page or open the file and runs code in the context of the current process.
The record
- CVE
- CVE-2021-27031
- Published
- Apr 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Autodesk
- Product
- FBX Review
- Classifications
- CWE-416, 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.
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