CVE-2016-9305
First published: Wed Jan 25 2017(Updated: )
Improper handling in the Autodesk FBX-SDK before 2017.1 of type mismatches and previously deleted objects related to reading and converting malformed FBX format files can allow attackers to gain access to uninitialized pointers.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Autodesk FBX SDK | <=2017.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-9305?
CVE-2016-9305 is classified as a high severity vulnerability due to improper handling of type mismatches.
How do I fix CVE-2016-9305?
To mitigate CVE-2016-9305, upgrade to Autodesk FBX SDK version 2017.1 or later.
What type of attack can be executed using CVE-2016-9305?
Attackers can exploit CVE-2016-9305 to gain access to uninitialized pointers by processing malformed FBX files.
Which versions of Autodesk FBX SDK are affected by CVE-2016-9305?
CVE-2016-9305 affects all versions of Autodesk FBX SDK prior to 2017.1.
What should users of Autodesk FBX SDK do in light of CVE-2016-9305?
Users of Autodesk FBX SDK should immediately upgrade to version 2017.1 or later to avoid potential exploitation of CVE-2016-9305.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/author
- agent/severity
- agent/weakness
- agent/softwarecombine
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/autodesk
- canonical/autodesk fbx sdk
- version/autodesk fbx sdk/2017.0