dbcve.org
KeyshotApplication · Luxion

CVE-2025-0412

HIGH · 7.8 CVSS v3.0 Published 2025-01-13
Fix available
A fix is available. Upgrade to 2023.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 Viewer KSP File Parsing Memory Corruption 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 processing of KSP files. The issue results from the lack of proper validation of user-supplied data, which can result in a memory corruption condition. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-22139.

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

Memory corruption vulnerability in Luxion KeyShot Viewer's KSP file parser due to insufficient validation of user-supplied data. The lack of bounds checking during KSP file parsing allows an attacker to write arbitrary data to memory, potentially achieving code execution in the context of the current user process.

MitigationDo not open untrusted KSP files from unknown sources. Apply vendor patches when available. Restrict file type associations and implement application whitelisting 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
KeyshotApplication
Affected:< 2023.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.0/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. Detect KeyShot installation
    Search for KeyShot in installed programs - check Program Files\Luxion or %ProgramFiles%\KeyShot for keyshot.exe, or use registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* for KeyShot entries
    Affected if KeyShot is present on the system
  2. Determine installed KeyShot version
    Right-click keyshot.exe in the KeyShot installation folder, select Properties, then Details tab to view File Version; alternatively run 'keyshot.exe -v' from command line if supported
    Affected if Version is present and less than 2023.3 (for example 2023.2, 2023.1, 2022, etc.)
  3. Check for KSP file type association
    Open Windows Registry and look under HKCR\.ksp to see if it points to KeyShot, or check HKCU\Software\Classes\.ksp or HKLM\Software\Classes\.ksp
    Affected if KSP file extension is associated with KeyShot Viewer
  4. Review user file handling behavior
    Check recent documents, recent files list, or Windows Jump List for .ksp file references; inspect browser download history for .ksp files
    Affected if User has recently opened or processed KSP files with KeyShot

User is affected if KeyShot version is installed and is lower than 2023.3, and the system or user processes KSP files through this application.

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

Do not open untrusted KSP files from unknown sources. Apply vendor patches when available. Restrict file type associations and implement application whitelisting as a defense-in-depth measure.

Recommended fix High confidence

KeyShot Viewer 2023.3 or later

  1. Navigate to the official KeyShot download page at download.keyshot.com
  2. Locate and download KeyShot Viewer version 2023.3 or later
  3. Close any running instances of KeyShot Viewer
  4. Install the updated version by running the downloaded installer
  5. Follow the installation prompts to complete the upgrade
  6. Verify the installed version is 2023.3 or newer by 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
  • 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-2025-0412 — 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-2025-0412 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