dbcve.org
KeyshotApplication · Luxion

CVE-2024-5506

HIGH · 7.8 CVSS v3.1 Published 2024-06-06
Fix available
A fix is available. Upgrade to 2024.1 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 Viewer KSP File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Luxion KeyShot Viewer. 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 KSP files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-22514.

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 · moderate confidence

A heap-based out-of-bounds write vulnerability exists in Luxion KeyShot Viewer's KSP file parser due to insufficient validation of user-supplied data during file parsing. The vulnerability allows an attacker to write past the boundary of an allocated buffer by crafting a malicious KSP file, potentially achieving arbitrary code execution in the context of the current process.

MitigationAvoid opening KSP files from untrusted or unknown sources. Apply vendor patches or updates to KeyShot Viewer when available. Alternatively, consider disabling file association handling or using 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.1
Keyshot Network RenderingApplication
Affected:< 2024.1
Keyshot ViewerApplication
Affected:< 2024.1

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 installed KeyShot products
    Check for Luxion KeyShot, KeyShot Network Rendering, or KeyShot Viewer installations in program directories (commonly C:\Program Files\Luxion or C:\Program Files\KeyShot) or via system inventory tools
    Affected if Any KeyShot product is installed
  2. Determine installed KeyShot version
    Locate the KeyShot executable (e.g., keyshot.exe, keyshot_viewer.exe) and check its version via file properties or using 'wmic product get name,version' if available
    Affected if Version is below 2024.1 (for example, 2023.x, 13.x, etc.)
  3. Verify KSP file handling is enabled
    Check Windows file association settings (HKEY_CLASSES_ROOT\.ksp) or Mac Finder Info for .ksp files to see if KeyShot is set as the handler, or look for KeyShot file preview plugins in the system
    Affected if KSP files are associated with or handled by the installed KeyShot Viewer or application
  4. Confirm KSP file parsing capability
    Attempt to open any .ksp file in the KeyShot Viewer application or observe if the application automatically processes KSP files upon file access
    Affected if The application can parse and render KSP files

You are affected if you have any KeyShot product (Viewer, Network Rendering, or main KeyShot) installed with a version below 2024.1 and the application handles KSP 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 2024.1 or later
Fixed in 2024.1
Interim mitigation

Avoid opening KSP files from untrusted or unknown sources. Apply vendor patches or updates to KeyShot Viewer when available. Alternatively, consider disabling file association handling or using application sandboxing to limit exposure.

Recommended fix Moderate confidence

KeyShot 2024.1

  1. Check the current KeyShot version by opening KeyShot and navigating to Help > About KeyShot
  2. Visit the official KeyShot website at www.keyshot.com and navigate to the downloads or products section
  3. Locate and download KeyShot 2024.1 (or the latest stable version) for your platform
  4. Close any running KeyShot applications including KeyShot Viewer, Network Rendering, and related processes
  5. Run the downloaded installer with administrator privileges
  6. Follow the on-screen installation prompts to complete the upgrade
  7. Restart KeyShot applications after installation completes
  8. Verify the installed version is 2024.1 or later via Help > About

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

Fix this in Keyshot Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
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,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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