dbcve.org
KeyshotApplication · Luxion

CVE-2024-11577

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 SKP 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. 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 SKP 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-23685.

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 high-severity out-of-bounds write vulnerability exists in Luxion KeyShot's SKP file parser due to insufficient validation of user-supplied data during file parsing. An attacker can exploit this by crafting a malicious SKP file that, when opened by a victim, triggers a buffer overflow allowing arbitrary code execution in the context of the current process.

MitigationUsers should avoid opening untrusted SKP files and ensure KeyShot is updated to the vendor's latest patched version once available. Organizations should implement file type restrictions and sandboxing for untrusted 3D model files.

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 installation
    Check for KeyShot installation directory in Program Files (Windows) or Applications folder (macOS), or query installed programs via system inventory tools
    Affected if KeyShot is present on the system
  2. Determine installed KeyShot version
    Right-click KeyShot.exe, select Properties, then Details to view File Version; or run 'KeyShot -version' from command line if supported; or check Add/Remove Programs for version info
    Affected if Version cannot be determined or shows a number lower than 2024.3
  3. Compare version against affected range
    Parse the version number found in step 2 and compare numerically to 2024.3 (e.g., 2024.2, 2024.1, 13.x, 12.x are all less than 2024.3)
    Affected if Installed version is a release prior to 2024.3 (e.g., 2024.2, 2024.1, 2023.x, etc.)
  4. Confirm SKP file handling capability
    SKP (SketchUp) file support is built into KeyShot's core functionality and enabled by default; verify by opening KeyShot and checking File > Open or importing an SKP file
    Affected if KeyShot can open or import SKP files (this is the default state for any KeyShot installation)

A user is affected if KeyShot is installed with any version prior to 2024.3 and the software is capable of processing SKP files, which is the default behavior.

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 SKP files and ensure KeyShot is updated to the vendor's latest patched version once available. Organizations should implement file type restrictions and sandboxing for untrusted 3D model files.

Recommended fix High confidence

KeyShot 2024.3

  1. Back up any existing KeyShot projects and settings before upgrading
  2. Navigate to the official KeyShot download page at download.keyshot.com
  3. Download KeyShot version 2024.3 or later
  4. Run the installer and follow the on-screen prompts to complete the installation
  5. Launch KeyShot and verify the version number displays 2024.3 or higher

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

Fix this in Keyshot Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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