CVE-2024-30374
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 · uneditedLuxion 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-22449.
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 confidenceThis is an out-of-bounds write vulnerability in Luxion KeyShot Viewer's KSP file parser. The flaw results from insufficient validation of user-supplied data during KSP file parsing, allowing an attacker to write past the end of an allocated buffer and achieve arbitrary code execution in the context of the current process.
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< 2024.2< 2024.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine KeyShot product versionOpen KeyShot or KeyShot Viewer, then go to Help > About (or check the application's executable file properties in Windows Explorer). Alternatively, check the installed program in Add/Remove Programs.Affected if The displayed version is earlier than 2024.2 (e.g., 2024.1, 13.x, 12.x, etc.)
-
Identify if KeyShot Viewer is installedCheck for the presence of KeyShot Viewer executable (typically named KeyShotViewer.exe) in the installation directory, commonly found under C:\Program Files\Luxion\KeyShot Viewer\ or verify via Windows Programs and Features.Affected if KeyShot Viewer is installed with a version below 2024.2
-
Confirm KSP file handling is possibleThe KSP file parser is a core component that activates when the application opens .ksp files. Check if the application can be used to open or import KSP files by attempting to open a KSP file or verifying file association for .ksp extension.Affected if The application can open KSP files and the installed version is below 2024.2
You are affected if Luxion KeyShot or KeyShot Viewer version below 2024.2 is installed and the application can process KSP files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2024.2
Avoid opening untrusted KSP files and apply vendor patches or update to a fixed version of KeyShot Viewer once available. Implement application whitelisting as a defense-in-depth measure.
Keyshot/Keyshot Viewer 2024.2
- 1. Identify the current installed version of Keyshot or Keyshot Viewer on the system
- 2. Download Keyshot or Keyshot Viewer version 2024.2 or later from the official Luxion website or authorized distribution channel
- 3. Install the updated version following the vendor's standard installation procedures
- 4. Verify the installed version is 2024.2 or higher to confirm the vulnerability is addressed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30374 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-30374 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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