CVE-2020-37030
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-37030 is a high-severity Unquoted Search Path or Element (CWE-428) vulnerability in Getoutline (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 3th 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.
Outline Service version 1.3.3 is affected by CVE-2020-37030, an unquoted service path vulnerability (CWE-428) in the Windows service binary path located at C:\Program Files (x86)\Outline. This flaw allows local users to potentially execute arbitrary code with elevated system privileges, specifically LocalSystem permissions, during service startup. The vulnerability has a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating high impact on confidentiality, integrity, and availability with low complexity for local exploitation.
Local low-privileged users (PR:L) can exploit this vulnerability without user interaction by placing a malicious executable in a directory that precedes the legitimate service binary in the system's PATH search order, due to the unquoted path. Upon service startup, the injected malicious code executes with LocalSystem privileges, enabling full system compromise such as persistence, lateral movement, or data exfiltration on the affected Windows host.
Advisories and references, including those from VulnCheck detailing the unquoted service path issue and an Exploit-DB entry (exploit 48414) providing a proof-of-concept, highlight the vulnerability but do not specify patches in the available information. The official Outline site (getoutline.org) is referenced for further context on the software. Security practitioners should verify service paths, apply least privilege, and monitor for updates from the vendor.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-30957
Vulnerability Data
Outline Service 1.3.3 contains an unquoted service path vulnerability that allows local users to potentially execute arbitrary code with elevated system privileges. Attackers can exploit the unquoted binary path in C:\Program Files (x86)\Outline to inject malicious code that would execute…
more
with LocalSystem permissions during service startup.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Unquoted service path directly enables path interception by unquoted path (T1574.009) for local privilege escalation (T1068) to LocalSystem.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Establishes and enforces secure configuration settings for services, including properly quoted binary paths to directly prevent exploitation of unquoted service path vulnerabilities.
Requires identification, reporting, and timely correction of system flaws such as unquoted service paths, enabling remediation to eliminate the vulnerability.
Enforces least privilege for services, reducing the impact of malicious code execution via unquoted paths by limiting privileges to the minimum necessary.
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.