Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2024-50986 is a high-severity Untrusted Search Path (CWE-426) vulnerability in Clementine-Player Clementine. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked in the top 41% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and CM-7 (Least Functionality) — 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.
Clementine version 1.3.1 contains an untrusted search path vulnerability tracked as CVE-2024-50986 and assigned CWE-426. The flaw permits a local attacker to place a crafted DLL that the application loads at runtime, resulting in arbitrary code execution on the host system. The issue carries a CVSS 3.1 score of 7.3 reflecting local attack vector, low attack complexity, and high impact across confidentiality, integrity, and availability.
A local attacker with the ability to write files to a location searched by Clementine can exploit the weakness when a user launches the player. Successful exploitation grants the attacker the same privileges as the running process, enabling full control over the affected workstation without requiring network access or elevated privileges beyond standard user rights.
The EPSS score for this CVE stands at 0.1085 with no material increase observed since disclosure. Public references consist of the Clementine project repository, the project homepage, and a proof-of-concept repository, but no vendor advisory or patch information is included in the available data.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-45131
Vulnerability Data
An issue in Clementine v.1.3.1 allows a local attacker to execute arbitrary code via a crafted DLL file.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Secure baseline settings can enforce absolute, organization-controlled paths for critical resources.
Least-functionality configuration can prohibit unapproved directories or executables from being reachable via search paths.
Engineering principles such as trusted paths, complete mediation, and least privilege directly require hard-coded or validated search paths instead of external ones.
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.
Preventing execution of unauthorized code directly blocks the malicious binaries that an untrusted search path would load.
Secure development practices include avoiding or sanitizing externally influenced search paths in application code.
Hardened configuration baselines can enforce safe search paths and restrict environment variables that enable the weakness.
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.
Security testing can discover search-path issues but does not itself prevent them in production code.
Restricting software installation reduces the chance that untrusted binaries or libraries are placed in search paths.
Secure architecture principles include hard-coded or validated search paths and avoiding reliance on untrusted directories.
Secure coding standards require absolute paths or integrity-checked search paths, directly mitigating CWE-426.
Change-management processes can enforce review of path-handling changes, indirectly lowering risk.