Code execution via altered FBX parser values
Published Apr 17, 2020 · Updated Aug 4, 2024
Heap overflow in the Autodesk FBX SDK 2019.5 and earlier allows attackers to execute code by supplying a malicious FBX file. Autodesk identifies the FBX parser and altered file values but does not disclose the specific parsing operation that overruns heap memory. Execution requires an application or service built with the SDK to parse the file, typically after user interaction, and occurs in that process.
Summary
What happened
Heap overflow in the Autodesk FBX SDK 2019.5 and earlier allows attackers to execute code by supplying a malicious FBX file. Autodesk identifies the FBX parser and altered file values but does not disclose the specific parsing operation that overruns heap memory. Execution requires an application or service built with the SDK to parse the file, typically after user interaction, and occurs in that process.
The record
- CVE
- CVE-2020-7085
- Published
- Apr 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- Autodesk
- Product
- FBX SDK
- Classifications
- CWE-787, T1566.001, 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.2 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