CVE-2020-36930
BaseFortify
Publication date: 2026-01-16
Last updated on: 2026-02-09
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| flexense | sysgauge | 7.9.18 |
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 SysGauge Server version 7.9.18. The executable path for the service is not enclosed in quotes, which allows local attackers to place malicious executables in certain path segments. When the service starts, the system might execute the malicious executable instead of the intended one, enabling the attacker to run arbitrary code and escalate their privileges on the system. [1, 2]
How can this vulnerability impact me? :
If exploited, this vulnerability can allow a local attacker with limited privileges to execute arbitrary code with higher privileges. This can lead to privilege escalation, compromising the confidentiality, integrity, and availability of the affected system. The attacker could gain unauthorized access, modify system files, or disrupt system operations. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for unquoted service paths in the SysGauge Server service configuration. You can use Windows Management Instrumentation Command-line (WMIC) and Service Control (sc) commands to query services with automatic start modes and identify unquoted paths. For example, use the command: wmic service get name,pathname,startmode | findstr /i "SysGauge" to find the service path, and then check if the path is unquoted. Additionally, use sc qc "SysGauge Server" to query the service configuration and verify if the binary path is unquoted. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, you should quote the service binary path in the SysGauge Server service configuration to prevent the system from misinterpreting the path and executing malicious executables. Alternatively, ensure that no malicious executables exist in any of the path segments that could be exploited. Applying the latest patches or updates from the vendor, if available, is also recommended to fix the unquoted service path issue. [2]