CVE-2020-37030
Unquoted Service Path in Outline 1.3.3 Enables Privilege Escalation
Publication date: 2026-01-30
Last updated on: 2026-01-30
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unknown_vendor | outline_service | to 1.3.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-428 | The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2020-37030 is an unquoted service path vulnerability in Outline Service version 1.3.3. The service's executable path contains spaces but lacks quotation marks, which allows local users with limited privileges to inject malicious code into the service path. When the service starts, Windows may execute the malicious code with elevated LocalSystem privileges, enabling arbitrary code execution with high system-level access. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow a local attacker to escalate their privileges by executing arbitrary code with LocalSystem permissions. This means the attacker can gain unauthorized control over the affected system, potentially leading to full system compromise, data theft, or disruption of services. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking the service configuration for unquoted service paths. Commands such as `wmic service where "name='OutlineService'" get PathName` or `sc qc OutlineService` can be used to query the service path. If the path to the executable contains spaces and is not enclosed in quotes, the service is vulnerable to this unquoted service path issue. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include correcting the service path by enclosing it in quotation marks to prevent code injection. Alternatively, ensure that no malicious executables exist in any directories along the unquoted path. Restrict local user permissions to prevent placing malicious executables in these locations. Applying updates or patches from the vendor that address this issue is also recommended. [1, 2]