CVE-2023-53947
Unquoted Service Path in OCS Inventory NG 2.3.0.0 Enables Privilege Escalation
Publication date: 2025-12-19
Last updated on: 2025-12-19
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ocsinventory-ng | ocs_inventory_ng | * |
| ocsinventory-ng | ocs_inventory_ng | 2.3.0.0 |
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 OCS Inventory NG version 2.3.0.0. Because the service executable path is not enclosed in quotes, a local attacker can place a malicious executable in a directory path segment that Windows misinterprets. When the vulnerable service restarts, it executes the malicious executable with system-level privileges, allowing the attacker to escalate their privileges to SYSTEM. [2, 3]
How can this vulnerability impact me? :
An attacker with local access can exploit this vulnerability to execute arbitrary code with SYSTEM privileges on the affected system. This means the attacker can gain full control over the system, potentially leading to unauthorized access, data theft, system manipulation, or disruption of services. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect the unquoted service path vulnerability by checking for services with unquoted executable paths. Use the following commands on the affected Windows system: 1. To list services with unquoted paths: `wmic service get name,pathname,displayname,startmode | findstr /i auto | findstr /i /v "C:\Windows\\" | findstr /i /v '"'` 2. To query the specific vulnerable service configuration: `sc qc "OCS Inventory Service"` These commands help identify if the OCS Inventory Service has an unquoted path, indicating the vulnerability. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include upgrading OCS Inventory NG to version 2.3.1.0 or later, where the service path is properly quoted to prevent exploitation. Additionally, avoid restarting the vulnerable service until the patch is applied, and restrict local user access to prevent placing malicious executables in the service path. If upgrading is not immediately possible, manually quoting the service path in the service configuration can reduce risk. [2, 3]