CVE-2022-50929
Unquoted Service Path in Connectify Hotspot Enables Code Execution
Publication date: 2026-01-13
Last updated on: 2026-01-13
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| connectify | hotspot | 2018 |
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-2022-50929 is an unquoted service path vulnerability in Connectify Hotspot 2018's ConnectifyService executable. Because the service path contains spaces but is not enclosed in quotes, Windows may incorrectly interpret the path and execute a malicious executable placed by a local attacker in certain directories. This allows the attacker to execute arbitrary code with elevated privileges when the service starts. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow a local attacker with limited privileges to escalate their privileges by executing arbitrary code with elevated rights on the affected system. This can lead to full system compromise, including unauthorized access, modification, or disruption of system confidentiality, integrity, and availability. [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 if the ConnectifyService Windows service executable path is unquoted and contains spaces. On a Windows system, use the command: sc qc ConnectifyService. Look for the BINARY_PATH_NAME field and verify if the path is unquoted (e.g., C:\Program Files (x86)\Connectify\ConnectifyService.exe without quotes). An unquoted path with spaces indicates the vulnerability. Additionally, you can check for suspicious executables placed in directories along the service path such as C:\Program.exe. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include correcting the service executable path by adding quotes around the path in the service configuration to prevent Windows from misinterpreting the path. Alternatively, restrict write permissions on directories in the service path to prevent attackers from placing malicious executables. Ensure that only trusted administrators have the ability to modify files in these directories. Restart the service after applying fixes to ensure the corrected path is used. [1, 2]