CVE-2021-47874
Unquoted Service Path Vulnerability in VFS for Git Enables Privilege Escalation
Publication date: 2026-01-21
Last updated on: 2026-01-21
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| vfs_for_git | vfs_for_git | 1.0.21014.1 |
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-2021-47874 is an unquoted service path vulnerability in the GVFS.Service Windows service of VFS for Git version 1.0.21014.1. Because the service's executable path is not enclosed in quotes, local attackers can place malicious executables in certain directories along the service path. When the service starts or the system reboots, these malicious executables can be run with LocalSystem privileges, allowing attackers to execute arbitrary code with elevated rights. [1, 2]
How can this vulnerability impact me? :
This vulnerability can lead to privilege escalation on affected systems. An attacker with local access can exploit the unquoted service path to execute malicious code with LocalSystem privileges, which is the highest level of privilege on Windows systems. This can compromise system confidentiality, integrity, and availability by allowing unauthorized code execution, potentially leading to full system control. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect the vulnerability by checking if the GVFS.Service Windows service has an unquoted service path. On a Windows system, use the command: sc qc GVFS.Service. If the BINARY_PATH_NAME value is not enclosed in quotes and contains spaces (e.g., C:\Program Files\GVFS\GVFS.Service.exe), the service is vulnerable to unquoted service path attacks. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include correcting the service path by enclosing the executable path in quotes to prevent execution of malicious binaries. Alternatively, restrict write permissions on directories in the service path to prevent attackers from placing malicious executables. Also, ensure the system is rebooted after applying fixes to prevent exploitation during startup. [1, 2]