dbcve.org
Fbx Software Development KitApplication · Autodesk

CVE-2023-27911

HIGH · 7.8 CVSS v3.1 Published 2023-04-17
Fix available
A fix is available. Upgrade to 2020.3.4 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
A user may be tricked into opening a malicious FBX file that may exploit a heap buffer overflow vulnerability in Autodesk® FBX® SDK 2020 or prior which may lead to code execution.

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

A heap buffer overflow vulnerability exists in Autodesk FBX SDK 2020 and prior versions when parsing malicious FBX files. The SDK fails to properly validate buffer bounds during file parsing, allowing an attacker to overwrite heap memory by crafting a specially malformed FBX file, potentially achieving code execution.

MitigationAvoid opening FBX files from untrusted sources. Update to a patched version of the FBX SDK when released by Autodesk, or implement application-level file validation and sandboxing as a defense-in-depth measure.

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:>= 2020.0, < 2020.3.4

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 FBX SDK is in use
    Search for Autodesk FBX SDK files on the system, check application dependencies, or look for FBX-related libraries (e.g., libfbxsdk.so, fbxsdk.dll) in known SDK installation directories or application binary folders.
    Affected if The FBX SDK library is present on the system or linked into any installed applications.
  2. Locate the installed FBX SDK version
    Check the SDK installation directory for version files, examine the library binary metadata, or query the application if it exposes the SDK version through about/info dialogs or logs.
    Affected if A specific version number of the FBX SDK can be determined from the system.
  3. Compare installed version against affected range
    Compare the identified version to the affected range: versions 2020.0 through 2020.3.3 (inclusive) are vulnerable. Versions 2020.3.4 and later are patched.
    Affected if The installed FBX SDK version is 2020.0, 2020.1, 2020.2, 2020.3, 2020.3.1, 2020.3.2, or 2020.3.3.
  4. Determine if FBX file parsing is enabled
    Identify whether any installed applications or services use the FBX SDK to parse FBX files, particularly from external or untrusted sources. Check application configurations or documentation for FBX import/loading functionality.
    Affected if The system runs software that parses FBX files using the vulnerable SDK version.

You are affected if the Autodesk FBX SDK version 2020.0 through 2020.3.3 is installed and any application on your system uses it to parse FBX files.

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 2020.3.4 or later
Fixed in 2020.3.4
Interim mitigation

Avoid opening FBX files from untrusted sources. Update to a patched version of the FBX SDK when released by Autodesk, or implement application-level file validation and sandboxing as a defense-in-depth measure.

Recommended fix High confidence

FBX SDK 2020.3.4

  1. 1. Download the fixed FBX SDK version 2020.3.4 or later from the official Autodesk developer website
  2. 2. Replace all affected FBX SDK library files (DLLs, .so files, or static libraries) in your project with the updated versions
  3. 3. Rebuild your application or software that links against the FBX SDK
  4. 4. Retest your application to ensure FBX file loading functionality works correctly with the patched SDK
  5. 5. Distribute the updated application to end users to address the vulnerability

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

Fix this in Fbx Software Development Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-27911 — 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-2023-27911 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