Code execution via crafted FBX file parsing
Published Apr 17, 2020 · Updated Aug 4, 2024
Buffer overflow in Autodesk FBX SDK 2019.0 and earlier allows context-dependent attackers to execute arbitrary code through a crafted FBX file. Autodesk has not published the affected parser routine or the unchecked memory operation that overruns the buffer while the SDK processes file data. Exploitation requires a user or integrating service to parse the malicious file, after which code runs with the privileges of the affected process.
Summary
What happened
Buffer overflow in Autodesk FBX SDK 2019.0 and earlier allows context-dependent attackers to execute arbitrary code through a crafted FBX file. Autodesk has not published the affected parser routine or the unchecked memory operation that overruns the buffer while the SDK processes file data. Exploitation requires a user or integrating service to parse the malicious file, after which code runs with the privileges of the affected process.
The record
- CVE
- CVE-2020-7080
- Published
- Apr 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- Autodesk
- Product
- FBX SDK
- Classifications
- CWE-120, T1204.002
- Attack vector
- local
- 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