CVE-2021-47882
Unquoted Service Path in FreeLAN 2.2 Enables Local Code Execution
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 |
|---|---|---|
| freelan | freelan | 2.2 |
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
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, you should update the FreeLAN service configuration to enclose the executable path in quotes to prevent malicious executable injection. Alternatively, ensure that only trusted users have local access to the system to reduce the risk of exploitation. Applying any available patches or updates from the FreeLAN developers is also recommended. [1, 3]
Can you explain this vulnerability to me?
This vulnerability in FreeLAN 2.2 is an unquoted service path issue in its Windows service configuration. Because the path to the service executable is not enclosed in quotes, a local attacker can place a malicious executable in a location that the system checks before the legitimate service executable. When the service starts, the malicious executable is run with elevated LocalSystem privileges, allowing the attacker to execute arbitrary code on the system. [1, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability allows a local attacker to execute arbitrary code with elevated LocalSystem privileges on the affected system. This means the attacker can gain full control over the system, potentially compromising confidentiality, integrity, and availability of data and services. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking the Windows service configuration for unquoted service paths related to the FreeLAN service. Specifically, you can inspect the service executable path to see if it is unquoted, which allows for code injection. A common command to check the service path is: sc qc FreeLAN. Look for the BINARY_PATH_NAME field and verify if the path is enclosed in quotes. If it is not, the service is vulnerable. [1, 3]