Application crash via crafted FBX null dereference
Published Apr 17, 2020 · Updated Aug 4, 2024
NULL pointer dereference in Autodesk FBX SDK 2019.5 and earlier allows attackers to crash an application by opening a malicious FBX file. The SDK's FBX parser dereferences a null pointer while processing the crafted file, but Autodesk has not disclosed the affected function or malformed field. Exploitation requires a user or consuming service to process the file and causes only the hosting application to crash.
Summary
What happened
NULL pointer dereference in Autodesk FBX SDK 2019.5 and earlier allows attackers to crash an application by opening a malicious FBX file. The SDK's FBX parser dereferences a null pointer while processing the crafted file, but Autodesk has not disclosed the affected function or malformed field. Exploitation requires a user or consuming service to process the file and causes only the hosting application to crash.
The record
- CVE
- CVE-2020-7084
- Published
- Apr 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- Autodesk
- Product
- FBX SDK
- Classifications
- CWE-476, 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.
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