CVE-2024-11578
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 3DS File Parsing Stack-based Buffer Overflow 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 3DS files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-23693.
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 confidenceLuxion KeyShot contains a stack-based buffer overflow vulnerability in its 3DS file parser. The flaw stems from insufficient validation of user-supplied data length before copying it into a stack-based buffer, allowing attackers to overwrite stack memory and achieve remote 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.3CVSS 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.
-
Verify KeyShot installationCheck for KeyShot installation by searching for KeyShot in program files or checking registry for installed software. Look for keyshot.exe in typical installation paths like C:\Program Files\Luxion\KeyShot\ or C:\Program Files (x86)\Luxion\KeyShot\Affected if KeyShot is installed on the system
-
Determine installed KeyShot versionRight-click on keyshot.exe, select Properties, then go to the Details tab to view the File Version. Alternatively, run 'keyshot.exe -v' from command line if supported, or check Add/Remove Programs for the installed version.Affected if The installed version is lower than 2024.3 (e.g., 2024.2, 2024.1, earlier versions)
-
Check for 3DS file handling capabilityVerify that the 3DS import/parser module exists within the KeyShot installation. Check for associated DLLs or modules related to 3DS file parsing in the installation directory.Affected if The 3DS file parser module is present and loadable by KeyShot
-
Monitor for 3DS file processingReview KeyShot recent files list, application logs, or Windows Event Viewer for evidence of 3DS file imports. Check browser download history or network shares for recently opened 3DS files.Affected if Any 3DS files have been opened or imported into KeyShot recently
The system is affected if Luxion KeyShot version 2024.2 or earlier is installed and users have opened or could open untrusted 3DS files with the built-in 3DS parser.
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.3
Users should avoid opening untrusted or unverified 3DS files until an official patch is released by Luxion. Organizations should consider network isolation and file sandboxing for handling untrusted 3D content.
KeyShot 2024.3
- Navigate to the official KeyShot download page at download.keyshot.com
- Download KeyShot version 2024.3 or later
- Install the downloaded installer
- Restart KeyShot if the application is currently running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,016.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11578 — 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-11578 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