Code execution via type-confused FBX file parsing
Published Apr 17, 2020 · Updated Aug 4, 2024
Type confusion in Autodesk FBX SDK 2019.5 and earlier allows attackers to execute code after a user opens a malicious FBX file. The FBX file-processing path treats crafted data as an incompatible type, causing reads and writes outside the intended memory bounds. Exploitation requires user interaction and runs code with the processing application's privileges; malformed input can instead interrupt the application.
Summary
What happened
Type confusion in Autodesk FBX SDK 2019.5 and earlier allows attackers to execute code after a user opens a malicious FBX file. The FBX file-processing path treats crafted data as an incompatible type, causing reads and writes outside the intended memory bounds. Exploitation requires user interaction and runs code with the processing application's privileges; malformed input can instead interrupt the application.
The record
- CVE
- CVE-2020-7081
- Published
- Apr 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- Autodesk
- Product
- Autodesk FBX SDK
- Classifications
- CWE-843, T1203, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2020CVE 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=2019.0 and earlier
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