dbcve.org
KeyshotApplication · Luxion

CVE-2024-30375

HIGH · 7.8 CVSS v3.1 Published 2024-06-06
Fix available
A fix is available. Upgrade to 2024.2 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 Use-After-Free 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 validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-22515.

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 Use-After-Free vulnerability exists in Luxion KeyShot Viewer's KSP file parser. The parser fails to validate that an object still exists before performing operations on it, allowing an attacker to manipulate memory after an object has been freed. When a user opens a specially crafted malicious KSP file, the vulnerability can be triggered to achieve arbitrary code execution in the context of the current process.

MitigationApply the vendor patch when available. Until then, refrain from opening KSP files from untrusted sources, and consider using application sandboxing or virtualization to isolate KeyShot Viewer from critical system resources.

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.2
Keyshot ViewerApplication
Affected:< 2024.2

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 Luxion KeyShot is installed
    Check for KeyShot executable in common installation paths such as C:\Program Files\Luxion\KeyShot\ or look for KeyShot in the Start Menu. Also check Add/Remove Programs in Control Panel for KeyShot entries.
    Affected if KeyShot or KeyShot Viewer is present on the system
  2. Determine installed KeyShot version
    Right-click on the KeyShot or KeyShot Viewer executable (typically named keyshot.exe or keyshot_viewer.exe), select Properties, and check the File Version field on the Details tab. Alternatively, launch KeyShot and go to Help > About to view the version.
    Affected if The version shown is earlier than 2024.2 (for example, 2024.1, 2023, 2022, etc.)
  3. Verify KSP file handling capability
    Confirm that the installed KeyShot version can open .ksp files. Check if .ksp file association exists or if KeyShot can manually open KSP files via File > Open.
    Affected if KSP file support is available and the application can parse KSP files
  4. Check for untrusted KSP file processing
    Review recent file open activity or temporary folders for .ksp files that may have been opened, particularly from untrusted or unknown sources. Examine browser download histories or email attachments for KSP files.
    Affected if Any KSP files from untrusted sources have been opened with the vulnerable version

A system is affected if Luxion KeyShot or KeyShot Viewer version 2024.1 or earlier is installed and the KSP file parser has been used to open a malicious KSP file.

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.2 or later
Fixed in 2024.2
Interim mitigation

Apply the vendor patch when available. Until then, refrain from opening KSP files from untrusted sources, and consider using application sandboxing or virtualization to isolate KeyShot Viewer from critical system resources.

Recommended fix High confidence

KeyShot 2024.2

  1. Backup any existing KeyShot projects and configurations before upgrading
  2. Download KeyShot 2024.2 or later from the official Luxion website (luxion.com/products/keyshot)
  3. Run the KeyShot installer and follow the on-screen prompts to complete the installation
  4. Launch KeyShot and verify the version number displays 2024.2 or higher
  5. Test that existing KSP files open correctly in the updated version
Caveat Review release notes for 2024.2 for any compatibility changes with plugins or workflow features

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

Fix this in Keyshot Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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