CVE-2021-47805
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 |
|---|---|---|
| disk_savvy | disk_savvy | 13.6.14 |
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 Disk Savvy version 13.6.14 on Windows. The service binaries are configured with paths that contain spaces but lack quotation marks, allowing local attackers to place malicious executables in certain path segments. When the service starts, Windows may execute these malicious executables with elevated LocalSystem privileges, enabling arbitrary code execution. [1, 3]
How can this vulnerability impact me? :
If exploited, this vulnerability allows a local attacker to execute arbitrary code with elevated LocalSystem privileges on the affected system. This can lead to full system compromise, unauthorized access, and control over the system, potentially allowing the attacker to install malware, steal data, or disrupt system operations. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by inspecting the service binary paths for unquoted spaces in the Disk Savvy services. You can use Windows Management Instrumentation Command-line (WMIC) and Service Control (sc) commands to list services with auto-start mode and check their executable paths. For example, use the command `wmic service where "startmode='auto'" get name,pathname` to list services and their paths, then look for unquoted paths containing spaces such as `C:\Program Files\Disk Savvy Server\bin\disksvs.exe`. Additionally, `sc qc <service_name>` can be used to query the configuration of a specific service to verify if the binary path is unquoted. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include correcting the unquoted service paths by enclosing the entire executable path in quotation marks to prevent Windows from misinterpreting the path and executing malicious code. Alternatively, restrict local user permissions to prevent unauthorized users from placing executables in the vulnerable path segments. Applying any available patches or updates from the vendor that address this issue is also recommended. [1, 3]