CVE-2023-54336
Unquoted Service Path in Mediconta 3.7.27 Enables Privilege Escalation
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 |
|---|---|---|
| infonetsoftware | mediconta | 3.7.27 |
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-2023-54336 is an unquoted service path vulnerability in Mediconta 3.7.27's Windows service named 'servermedicontservice'. Because the service executable path contains spaces and is not enclosed in quotes, a local attacker can place a malicious executable in a directory path that the system searches before the legitimate service executable. When the service starts, the malicious code can be executed with elevated LocalSystem privileges, allowing privilege escalation. [1, 3]
How can this vulnerability impact me? :
This vulnerability allows a local attacker to execute arbitrary code with LocalSystem privileges on the affected system. This means the attacker can gain elevated access, potentially compromising the entire system, installing malware, or performing unauthorized actions that require high-level permissions. [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 configuration for unquoted service paths. Specifically, you can check the 'servermedicontservice' service executable path to see if it is unquoted and contains spaces. Commands such as 'wmic service where name="servermedicontservice" get PathName' or 'sc qc servermedicontservice' can be used to view the service executable path and confirm if it is unquoted. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include correcting the service executable path by enclosing it in quotes to prevent path hijacking. Alternatively, ensure that no malicious executables exist in directories that precede the legitimate service path in the system's search order. Restrict local user permissions to prevent unauthorized file placement in these directories. Applying vendor patches or updates, if available, is also recommended. [1, 3]