Executive Summary

CVE-2022-50917 is an unquoted service path vulnerability in ProtonVPN version 1.26.0's WireGuard service configuration. Because the executable path contains spaces but is not enclosed in quotes, Windows may misinterpret the path and execute a malicious executable placed by a local attacker in certain file system locations. This allows the attacker to run arbitrary code with elevated privileges when the service starts. [2, 3]

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can allow a local attacker to execute arbitrary code with elevated privileges on the affected system. Since the ProtonVPN WireGuard service runs under the LocalSystem account, exploitation can lead to full system compromise, including unauthorized access, modification, or disruption of system confidentiality, integrity, and availability. [2, 3]

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by checking the ProtonVPN WireGuard service configuration for unquoted service paths containing spaces. On a Windows system, you can use the command: `sc qc ProtonVPN.WireGuardService` to query the service configuration and inspect the executable path. If the path is unquoted and contains spaces (e.g., C:\Program Files (x86)\Proton Technologies\ProtonVPN\ProtonVPN.WireGuardService.exe ...), the system is vulnerable. Additionally, you can manually inspect the service executable path in the Services MMC snap-in or via PowerShell using `Get-WmiObject win32_service | where {$_.Name -eq 'ProtonVPN.WireGuardService'}` and check the PathName property for unquoted paths. [3]

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include correcting the service executable path by adding quotes around the full path in the ProtonVPN WireGuard service configuration to prevent Windows from misinterpreting the path. Alternatively, updating ProtonVPN to a version where this vulnerability is fixed is recommended. As a temporary measure, restrict local user access to directories where malicious executables could be placed (e.g., C:\) to prevent exploitation. Monitoring and removing any suspicious executables placed in parent directories can also help mitigate risk. [2, 3]

Useful 0 Not Useful 0