CVE-2020-36989 Overview
ForensiT AppX Management Service version 2.2.0.4 contains an unquoted service path vulnerability (CWE-428) that allows local users to potentially execute arbitrary code with elevated system privileges. Attackers can exploit the unquoted path in the service configuration to inject malicious code that would execute with LocalSystem account permissions during service startup.
Critical Impact
Local attackers with write access to specific directories in the service path can achieve privilege escalation to SYSTEM-level access, potentially compromising the entire system.
Affected Products
- ForensiT AppX Management Service 2.2.0.4
Discovery Timeline
- 2026-01-28 - CVE CVE-2020-36989 published to NVD
- 2026-01-29 - Last updated in NVD database
Technical Details for CVE-2020-36989
Vulnerability Analysis
This vulnerability is classified as an Unquoted Search Path or Element vulnerability (CWE-428). When the Windows Service Control Manager (SCM) attempts to start the ForensiT AppX Management Service, it parses the unquoted executable path. If the path contains spaces and is not properly enclosed in quotation marks, Windows interprets each space as a potential delimiter between the executable path and its arguments.
An attacker with local access can plant a malicious executable in a location along the unquoted service path that Windows will execute before reaching the intended service binary. When the service starts (either manually or at system boot), the malicious executable runs with the privileges of the service account—in this case, LocalSystem, which provides complete control over the system.
Root Cause
The root cause of this vulnerability lies in the improper service path configuration during installation of the ForensiT AppX Management Service. The service executable path was registered in the Windows Registry without surrounding quotation marks. When a path contains spaces (such as C:\Program Files\...), Windows requires the path to be quoted to prevent ambiguous parsing. The absence of these quotes creates an exploitable condition where attackers can intercept the service execution flow.
Attack Vector
The attack vector is local, requiring an authenticated attacker to have write permissions to directories along the service path before any space character. Common exploitation scenarios include:
- The attacker identifies the unquoted service path using tools like wmic service get name,displayname,pathname,startmode or sc qc commands
- The attacker determines which intermediate paths they have write access to (e.g., C:\Program.exe if write access to C:\ exists, or executables in directories before spaces in the path)
- A malicious payload is placed in one of these locations with a name that matches the truncated path segment
- Upon service restart or system reboot, the malicious executable is invoked with SYSTEM privileges instead of or before the legitimate service binary
For additional technical details and a proof-of-concept, refer to Exploit-DB #48821.
Detection Methods for CVE-2020-36989
Indicators of Compromise
- Unexpected executable files appearing in root directories or program folders (e.g., C:\Program.exe, C:\Program Files\ForensiT.exe)
- Service-related errors in Windows Event Logs indicating unexpected service behavior
- Unusual processes running with SYSTEM privileges that don't match expected service binaries
- New or modified files in directories along the ForensiT AppX Management Service path
Detection Strategies
- Query all Windows services for unquoted paths using wmic service get name,displayname,pathname,startmode | findstr /i /v """ to identify vulnerable services
- Monitor file system activity in directories along service paths for suspicious executable creation
- Implement application whitelisting to prevent unauthorized executables from running with elevated privileges
- Deploy endpoint detection and response (EDR) solutions like SentinelOne to detect privilege escalation attempts and unauthorized service modifications
Monitoring Recommendations
- Enable Windows Security Event logging for service configuration changes (Event ID 7045 for new service installations)
- Monitor Windows Registry keys under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ForensITAppXService for unauthorized modifications
- Configure alerts for process creation events where parent processes are services and child processes are in unexpected locations
- Regularly audit service configurations across endpoints to identify unquoted service paths
How to Mitigate CVE-2020-36989
Immediate Actions Required
- Audit the ForensiT AppX Management Service installation on affected systems to confirm the vulnerable configuration
- Restrict write permissions on directories along the service executable path to administrators only
- Check for any unauthorized executables that may have been placed in exploitable path locations
- Consider disabling the service until the path can be properly quoted in the registry
Patch Information
ForensiT users should visit the ForensIT Download Page to check for updated versions that address this vulnerability. Additionally, review the VulnCheck Advisory for further remediation guidance.
Workarounds
- Manually correct the service path by adding quotation marks around the executable path in the Windows Registry
- Restrict write access to all directories in the service path using NTFS permissions
- Implement application control policies to prevent execution of unauthorized binaries in sensitive directories
- Deploy SentinelOne endpoint protection to detect and block exploitation attempts in real-time
# Registry fix to quote the service path (run as Administrator)
# First, identify the current ImagePath value:
reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ForensITAppXService" /v ImagePath
# Then update with properly quoted path (adjust path as needed for your installation):
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ForensITAppXService" /v ImagePath /t REG_EXPAND_SZ /d "\"C:\Program Files\ForensIT\AppX Management Service\ForensITAppXService.exe\"" /f
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

