Cyber Resilience

CVE-2025-0412

Memory Safety in Luxion Keyshot ≤ 2023.3

Published
13 January 2025
Modified
07 August 2025
Patch / advisory
CVSS Score v3 7.8
Click a component to see what it means
Raw vectorCVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0037 30th percentile
Risk Priority 61 floored blend · peak EPSS

Summary

CVE-2025-0412 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Luxion Keyshot. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Process Injection (T1055); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-8 (Security and Privacy Engineering Principles) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-0412 is a memory corruption vulnerability in Luxion KeyShot Viewer that occurs during parsing of KSP files. The flaw stems from insufficient validation of user-supplied data and can be triggered when the application processes a malicious file, resulting in remote code execution in the context of the current process. It carries a CVSS 7.8 score and is tracked under CWE-119; the issue was originally reported as ZDI-CAN-22139.

An unauthenticated remote attacker can exploit the vulnerability by convincing a target to open a crafted KSP file or visit a malicious page hosting such a file. Successful exploitation grants arbitrary code execution without additional privileges beyond the user's context, though user interaction is required.

Public advisories from Luxion and the Zero Day Initiative, available at the referenced URLs, address the issue and should be consulted for patch availability and recommended mitigation steps. The associated EPSS score has remained flat at 0.0233 with no material increase observed after disclosure.

EU & UK References

Vulnerability Data

Luxion KeyShot Viewer KSP File Parsing Memory Corruption 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…

more

must visit a malicious page or open a malicious file. The specific flaw exists within the processing of KSP files. The issue results from the lack of proper validation of user-supplied data, which can result in a memory corruption condition. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-22139.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1055 Process Injection Stealth
Adversaries may inject code into processes in order to evade process-based defenses as well as possibly elevate privileges.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-1045Same product: Luxion Keyshot
CVE-2025-1046Same product: Luxion Keyshot
CVE-2025-2532Same product: Luxion Keyshot
CVE-2024-11581Same product: Luxion Keyshot
CVE-2025-1047Same product: Luxion Keyshot
CVE-2024-11578Same product: Luxion Keyshot
CVE-2025-2531Same product: Luxion Keyshot
CVE-2024-11577Same product: Luxion Keyshot
CVE-2024-11576Same product: Luxion Keyshot
CVE-2024-11580Same product: Luxion Keyshot

Affected Assets

luxion
keyshot
≤ 2023.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V17.3.2

Mitigating Controls (NIST 800-53 r5) AI

Secure engineering principles require memory-safe design and coding that structurally avoids buffer-boundary violations.

Input validation directly enforces bounds checking that stops out-of-bounds reads/writes from being introduced or reached.

Memory protection restricts exploitation impact of buffer overflows without eliminating the underlying coding flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices (bounds checking, safe APIs, reviews) directly prevent this class of flaw.

ID.RA-01 partial match
prevents

Vulnerability scanning and code analysis directly surface buffer-boundary flaws.

ID.RA-08 partial match
prevents

Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.

PR.AT-02 partial match
prevents

Developer training on secure coding reduces introduction of memory-buffer errors.

PR.PS-02 partial match
prevents

Patching replaces vulnerable code containing buffer-boundary defects.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches out-of-bounds accesses before release, covering most instances of the weakness.

prevents

Secure development lifecycle mandates memory-safety practices that directly prevent buffer-boundary violations.

prevents

Application security requirements can specify memory-safety rules, but do not prescribe implementation details.

prevents

Secure architecture and engineering principles include memory-safe design patterns that mitigate buffer overflows.

prevents

Secure coding standards explicitly forbid unsafe buffer operations, directly eliminating CWE-119.

References