dbcve.org
Fbx Software Development KitApplication · Autodesk

CVE-2016-9307

CRITICAL · 9.8 CVSS v3.0 Published 2017-01-25
Fix available
A fix is available. Upgrade to after 2017.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Multiple buffer overflows in the Autodesk FBX-SDK before 2017.1 can allow attackers to execute arbitrary code when reading or converting malformed 3DS format files.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple buffer overflow vulnerabilities exist in the Autodesk FBX-SDK versions prior to 2017.1 when parsing malformed 3DS format files. These overflows occur during file reading or conversion operations and can be exploited to achieve arbitrary code execution on the target system.

MitigationUpdate Autodesk FBX-SDK to version 2017.1 or later to patch the buffer overflow vulnerabilities. Validate all 3DS file processing code paths after the update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Fbx Software Development KitApplication
Affected:<= 2017.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Autodesk FBX-SDK is installed
    Search for FBX-SDK installation directories or libraries on the system. Common locations include /usr/local/fbx, C:\Program Files\Autodesk\FBX, or within application bund directories. Check for files named libfbxsdk, fbxsdk.dll, or FBXSDK libraries.
    Affected if Autodesk FBX-SDK files or libraries are found on the system
  2. Determine the installed FBX-SDK version
    Locate version information within the FBX-SDK installation. Check for a version.h, version.txt, or version file in the SDK directory. Alternatively, inspect the DLL/library properties if a fbxsdk.dll or libfbxsdk.so is found. Compare the version number to the affected range.
    Affected if The installed version is 2017.0 or earlier, or no version information is found indicating an older installation
  3. Identify applications using FBX-SDK for 3DS file processing
    Review applications that handle 3DS format files (3D Studio files) on the system. Search for software that imports, exports, or converts 3DS files. Check application logs or documentation for FBX-SDK dependency information.
    Affected if Applications that process 3DS format files using FBX-SDK are in use
  4. Verify if file reading or conversion operations are performed on untrusted 3DS files
    Audit the workflow for 3DS file handling. Identify whether the system processes 3DS files from external or untrusted sources through FBX-SDK conversion functions. Review any file import pipelines that invoke FBX-SDK APIs.
    Affected if 3DS files from external or untrusted sources are processed through FBX-SDK file reading or conversion functions

The environment is affected if Autodesk FBX-SDK version 2017.0 or earlier is installed and the system processes or converts 3DS format files using the SDK.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2017.0
Interim mitigation

Update Autodesk FBX-SDK to version 2017.1 or later to patch the buffer overflow vulnerabilities. Validate all 3DS file processing code paths after the update.

Recommended fix High confidence

FBX-SDK 2017.1

  1. Identify all applications and systems using the Autodesk FBX-SDK version 2017.0 or earlier
  2. Obtain the FBX-SDK version 2017.1 or later from the official Autodesk developer website
  3. Replace the vulnerable SDK binaries and header files in your project with the updated version
  4. Recompile and rebuild any applications that link against the FBX-SDK
  5. Test that 3DS file reading and conversion functionality works correctly with the updated SDK
  6. Deploy the rebuilt applications to production environments
Caveat Review SDK release notes for any API changes between your current version and 2017.1

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fbx Software Development Kit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-9307 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-9307 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data