CVE-2024-11580
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 ABC File Parsing Heap-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 abc files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-23700.
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 confidenceHeap-based buffer overflow in Luxion KeyShot's ABC file parser due to insufficient validation of user-supplied data length before copying to a heap-based buffer. The vulnerability allows remote code execution in the context of the current process when a user opens a malicious ABC file.
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 if Luxion KeyShot is installedCheck common installation paths: C:\Program Files\Luxion\KeyShot* or C:\Program Files (x86)\Luxion\KeyShot* on Windows. On macOS, check /Applications/ for KeyShot.app. Use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*KeyShot*'}Affected if KeyShot is found installed on the system
-
Determine installed KeyShot versionRight-click the KeyShot executable, select Properties, then look at the Details tab for Product Version. Or run KeyShot and go to Help > About KeyShot. Command line: (Get-Item 'C:\Program Files\Luxion\KeyShot*\KeyShot.exe').VersionInfo.FileVersionAffected if The version number is less than 2024.3 (for example, 2024.2, 2024.1, 13.x, etc.)
-
Confirm ABC file import capability is in useCheck for .abc file associations or recent files. On Windows, check: Get-ChildItem -Path $env:USERPROFILE -Recurse -Filter '*.abc' -ErrorAction SilentlyContinue | Select-Object -First 10 FullName, LastWriteTime. Also check KeyShot's recent files list if accessible.Affected if ABC files exist on the system or have been opened recently, indicating the vulnerable parser code path could be triggered
-
Inspect KeyShot file type associationsCheck Windows registry for .abc file type handler: Get-ItemProperty 'HKCR:\.abc' -ErrorAction SilentlyContinue. Also check HKCR:\SystemFileAssociations\.abc for application bindings.Affected if KeyShot is registered as a handler for .abc files, meaning double-clicking a malicious ABC file would trigger the vulnerable code path
You are affected if KeyShot is installed with a version lower than 2024.3 AND the system processes or associates with ABC files, as the heap overflow occurs when a malicious ABC file is opened.
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
Validate the length of user-supplied data against the destination buffer size before copying in the ABC file parsing routines. Consider implementing bounds checking and using safe memory copy functions.
KeyShot 2024.3 or later
- Navigate to the official KeyShot download page at download.keyshot.com
- Download KeyShot version 2024.3 or the latest available version
- Verify the downloaded installer matches the official KeyShot distribution
- Close any running KeyShot instances
- Run the installer and follow the prompts to upgrade the software
- Restart the application after installation completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11580 — 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-11580 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