Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-11578: CWE-121: Stack-based Buffer Overflow in Luxion KeyShot

0
High
VulnerabilityCVE-2024-11578cvecve-2024-11578cwe-121
Published: Fri Nov 22 2024 (11/22/2024, 20:43:54 UTC)
Source: CVE Database V5
Vendor/Project: Luxion
Product: KeyShot

Description

Luxion 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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 06:42:02 UTC

Technical Analysis

CVE-2024-11578 is a stack-based buffer overflow vulnerability identified in Luxion KeyShot, a popular 3D rendering and visualization software. The vulnerability specifically affects the 3DS file parser in version 2024 13.0.0 Build 92 4.10.171. The root cause is the lack of proper validation of the length of user-supplied data before copying it into a stack-based buffer, leading to a classic buffer overflow condition (CWE-121). When a maliciously crafted 3DS file is processed, the overflow can overwrite the stack, allowing an attacker to execute arbitrary code with the privileges of the KeyShot process. Exploitation requires user interaction, such as opening a malicious file or visiting a malicious webpage that triggers the file parsing. The vulnerability has a CVSS v3.0 score of 7.8, indicating high severity, with impacts on confidentiality, integrity, and availability. Although no active exploits have been reported, the vulnerability poses a significant risk due to the potential for remote code execution. The issue was tracked as ZDI-CAN-23693 and publicly disclosed on November 22, 2024. The absence of a patch link suggests that a fix may still be pending or in development, emphasizing the need for immediate mitigation steps.

Potential Impact

This vulnerability allows remote attackers to execute arbitrary code on affected systems running Luxion KeyShot, potentially leading to full compromise of the application and possibly the underlying system depending on the execution context and privileges. The attacker could steal sensitive data processed or stored by KeyShot, alter or corrupt 3D models and rendering outputs, or disrupt service availability by crashing the application. Given KeyShot's use in design, manufacturing, and visualization workflows, exploitation could result in intellectual property theft, sabotage of design assets, and operational downtime. The requirement for user interaction limits automated widespread exploitation but targeted attacks against organizations relying on KeyShot are feasible. The high CVSS score reflects the critical impact on confidentiality, integrity, and availability, combined with relatively low attack complexity and no need for privileges but requiring user action.

Mitigation Recommendations

1. Immediately monitor Luxion's official channels for patches or updates addressing CVE-2024-11578 and apply them as soon as they become available. 2. Until a patch is released, restrict the opening of untrusted or unsolicited 3DS files within KeyShot environments, especially from unknown or external sources. 3. Implement application whitelisting and sandboxing for KeyShot to limit the impact of potential exploitation. 4. Educate users about the risks of opening files from untrusted sources and the importance of verifying file origins. 5. Employ network-level controls to block access to malicious websites that could host exploit files or trigger malicious file downloads. 6. Use endpoint detection and response (EDR) tools to monitor for anomalous behavior indicative of exploitation attempts, such as unexpected process spawning or memory corruption indicators. 7. Consider disabling or limiting 3DS file support temporarily if feasible within operational constraints. 8. Conduct regular backups of critical design data to enable recovery in case of compromise.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
zdi
Date Reserved
2024-11-20T22:00:49.233Z
Cvss Version
3.0
State
PUBLISHED

Threat ID: 699f6e18b7ef31ef0b5950f4

Added to database: 2/25/2026, 9:48:08 PM

Last enriched: 2/26/2026, 6:42:02 AM

Last updated: 4/12/2026, 3:33:14 PM

Views: 25

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses