CVE-2020-37059
Unquoted Service Path in Popcorn Time Allows 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 |
|---|---|---|
| popcorn_time | popcorn_time | 6.2.1.14 |
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-37059 is an unquoted service path vulnerability in Popcorn Time version 6.2.1.14. This flaw allows local non-privileged users to execute arbitrary code with elevated SYSTEM-level privileges by placing malicious executables in directories like "Program Files (x86)" or the system root. Because the service path is unquoted and contains spaces, the system may incorrectly resolve the executable path during service startup, leading to privilege escalation. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow a local attacker with limited privileges to escalate their rights to SYSTEM-level privileges on the affected machine. By exploiting the unquoted service path, an attacker can execute malicious code with the highest system privileges, potentially leading to full system compromise, unauthorized access, and control over the system. [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 an unquoted service path. On Windows, use the command: sc qc "Update service". This command will show the binary path of the service. If the path is unquoted and contains spaces (e.g., C:\Program Files (x86)\Popcorn Time\Updater.exe), the system 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 quoting the executable path in the service configuration to prevent the system from misinterpreting the path. Additionally, restrict write permissions to directories like "Program Files (x86)" and the system root to prevent local users from placing malicious executables. Applying any available updates or patches from the vendor is also recommended. [1, 2]