dbcve.org
KeyshotApplication · Luxion

CVE-2024-11576

HIGH · 7.8 CVSS v3.1 Published 2024-11-22
Fix available
A fix is available. Upgrade to 2024.3 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
Luxion KeyShot 3DS File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Luxion KeyShot. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of 3DS files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-23681.

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-based buffer overflow vulnerability exists in Luxion KeyShot's 3DS file parser. The application fails to validate the length of user-supplied data before copying it into a heap-allocated buffer, allowing an attacker to corrupt memory and achieve arbitrary code execution when a victim opens a malicious 3DS file.

MitigationUsers should avoid opening untrusted 3DS files until an official patch is released. Organizations should implement file type validation and consider application sandboxing to limit exposure.

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
KeyshotApplication
Affected:< 2024.3

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. Verify KeyShot is installed
    Check for KeyShot installation directory (commonly at C:\Program Files\Luxion\KeyShot\ or C:\Program Files\KeyShot\) or search for keyshot.exe using file explorer or PowerShell: Get-ChildItem -Path "C:\Program Files" -Recurse -Filter "keyshot.exe" -ErrorAction SilentlyContinue
    Affected if KeyShot executable is found on the system
  2. Determine installed KeyShot version
    Right-click keyshot.exe, select Properties, then view the Details tab for Product Version. Alternatively, launch KeyShot and check Help > About KeyShot for the exact version number
    Affected if Version is listed as lower than 2024.3 (for example, 2024.2, 2024.1, 13.x, 12.x, etc.)
  3. Check for recent 3DS file usage
    Review recently opened files in KeyShot (File > Recent Files) or search for .3ds files on the system using: Get-ChildItem -Path $env:USERPROFILE -Recurse -Filter "*.3ds" -ErrorAction SilentlyContinue | Select-Object -First 10 FullName, LastWriteTime
    Affected if User has opened or currently has 3DS model files processed by KeyShot

User is affected if KeyShot version is installed and the version is lower than 2024.3, and the system processes or has recently processed 3DS files with KeyShot

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

Users should avoid opening untrusted 3DS files until an official patch is released. Organizations should implement file type validation and consider application sandboxing to limit exposure.

Recommended fix Moderate confidence

KeyShot 2024.3

  1. 1. Close any running instances of KeyShot to ensure a safe update process
  2. 2. Navigate to the official KeyShot download page at download.keyshot.com
  3. 3. Download KeyShot version 2024.3 or later
  4. 4. Run the installer and follow the on-screen prompts to complete the upgrade
  5. 5. Verify the installed version by opening KeyShot and checking Help > About KeyShot

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

Fix this in Keyshot Scoped from the published advisory
  • Consultation2.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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