CVE-2021-47810
BaseFortify
Publication date: 2026-01-16
Last updated on: 2026-01-16
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wibu-systems | wibukey_runtime | 6.51 |
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?
This vulnerability is an unquoted service path issue in the WibuKey Runtime 6.51, specifically in the WkSvW32.exe service. Because the service executable path contains spaces and is not enclosed in quotes, local attackers can place malicious executables in the service path. When the service starts, Windows might execute the malicious code instead of the intended executable, allowing attackers to run arbitrary code and escalate their privileges on the affected system. [2, 4]
How can this vulnerability impact me? :
Exploiting this vulnerability can allow a local attacker to execute arbitrary code with elevated privileges, potentially leading to full system compromise. This means attackers can gain higher access rights than intended, affecting the confidentiality, integrity, and availability of the system and its data. [2, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking the service configuration for unquoted service paths. Specifically, you can use the Windows Management Instrumentation Command-line (WMIC) to list services with automatic start mode excluding those in the Windows directory to find unquoted paths. Additionally, the 'sc qc' command can be used to query the service configuration and verify if the binary path name is unquoted. For example, run 'wmic service where (startmode='auto' and pathname like '% %' and pathname not like 'C:\Windows%') get name,pathname,startmode' and then 'sc qc <service_name>' to check the path of the WkSvW32.exe service. [4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include correcting the unquoted service path by enclosing the executable path in double quotes to prevent execution of malicious executables. For the WkSvW32.exe service, update the service configuration to use the quoted path: "C:\PROGRAM FILES (X86)\WIBUKEY\SERVER\WkSvW32.exe". This can be done using the 'sc config' command or by editing the service registry entry. Additionally, ensure that only trusted users have write permissions to directories in the service path to prevent placing malicious executables. [4]