CVE-2020-37060
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2020-37060 is a high-severity Unquoted Search Path or Element (CWE-428) vulnerability in Drive Software (inferred from references). Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception by Unquoted Path (T1574.009); ranked at the 6th percentile by exploit likelihood (below the median); 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 SI-2 (Flaw Remediation) — 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-2020-37060 is a local privilege escalation vulnerability in Atomic Alarm Clock 6.3, stemming from an unquoted service path in its service configuration (CWE-428). This flaw enables attackers to execute arbitrary code with SYSTEM privileges. The vulnerability carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H) and was published on 2026-01-30.
Local attackers with low privileges can exploit the unquoted service path by placing a malicious executable named 'Program.exe' in a specific directory, causing the service to execute it instead of the legitimate binary upon startup. This achieves arbitrary code execution with SYSTEM privileges, enabling persistent system-level access.
Advisories, including those from VulnCheck and an Exploit-DB entry (48352), detail the unquoted service path issue in Atomic Alarm Clock. The vendor site is available at drive-software.com.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-30954
Vulnerability Data
Atomic Alarm Clock 6.3 contains a local privilege escalation vulnerability in its service configuration that allows attackers to execute arbitrary code with SYSTEM privileges. Attackers can exploit the unquoted service path by placing a malicious executable named 'Program.exe' to gain…
more
persistent system-level access.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Unquoted service path (CWE-428) directly enables path interception for privilege escalation to SYSTEM via malicious executable placement.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires identification, reporting, and correction of flaws like CVE-2020-37060, including patching the unquoted service path or removing the vulnerable service.
Mandates secure configuration settings for system components, ensuring service executable paths are quoted and parent directories are protected from unauthorized writes.
Enforces least privilege for accounts and processes, allowing the service to run with minimal necessary privileges to reduce the impact of escalation to SYSTEM.
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.
Secure SDLC practices directly prevent path-handling flaws such as unquoted elements during development.
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 in development can detect unquoted search-path issues before deployment.
Enforcing controlled software installation can prevent unquoted search-path elements in executables and scripts.
Secure development lifecycle practices include input validation and path handling that reduce unquoted search-path weaknesses.
Secure system architecture and engineering principles require safe path construction and quoting conventions.
Secure coding standards directly mandate quoting search paths and avoiding unsafe path construction.
Change-management processes can enforce review of path-handling changes that might introduce unquoted elements.