CVE-2020-36879
BaseFortify
Publication date: 2025-12-05
Last updated on: 2025-12-08
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| flexense | diskboss_enterprise | 11.7.28 |
| flexense | diskboss_pro | 11.7.28 |
| flexense | diskboss | 11.7.28 |
| flexense | diskboss_server | 11.7.28 |
| flexense | diskboss_ultimate | 11.7.28 |
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 in Flexsense DiskBoss 11.7.28 allows unauthenticated attackers to elevate their privileges by exploiting an unquoted service path. Attackers can specify a malicious service name using the 'sc qc' command, which leads to remote code execution during system startup or reboot with escalated privileges.
How can this vulnerability impact me? :
The vulnerability can allow attackers to execute arbitrary system commands with elevated privileges remotely, potentially compromising the affected system's security and control.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating DiskBoss to a fixed version if available, or manually correcting the service executable paths by enclosing them in quotes to prevent exploitation. Additionally, restrict low-privileged user access to directories in the service path to prevent placing malicious executables. Rebooting the system after applying fixes or updates will ensure the changes take effect. [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 using the Windows command `sc qc <service_name>`. Specifically, you should inspect the DiskBoss related services to see if their executable paths are unquoted and contain spaces, which can be exploited. For example, run commands like `sc qc DiskBossServiceName` replacing DiskBossServiceName with the actual service name to view the binary path and verify if it is unquoted. [2, 4]