Windows Unquoted Service Path Enumeration - Is this still a case in modern Windows (10, 11) ?

Frequent Contributor

Hi Folks, 


This could be irrelevant as the issue goes back to few years and Microsoft may have already fixed it but, just wanted verify/confirm. 

Windows Unquoted Path Enumeration vulnerability was identified back in 2013 (or may be even earlier). In simple terms, when a service is created whose executable path contains spaces and isn’t enclosed within quotes, leads to a vulnerability known as Unquoted Service Path which allows a user to gain SYSTEM privileges (only if the vulnerable service is running with SYSTEM privilege level which most of the time it is). In Windows, if the service is not enclosed within quotes and is having spaces, it would handle the space as a break and pass the rest of the service path as an argument.



So my question is, is this still a vulnerability in the modern versions of Windows 10,11?  


Appreciate any inputs/recommendations!



3 Replies

Apparently there still seems to be a lot of applications with this vulnerability out there but not necessarily mean that falls under Microsoft?. I'd imagine it simply means that you should update the application as soon as the 3rd party release a fix.


i.e. CVE - CVE-2022-27050 ( BitComet Service for Windows before version 1.8.6 contains an unquoted service path vulnerability.


Ref -

best response confirmed by Manoj Karunarathne (Frequent Contributor)
The above response is the latest on this as I could not fetch anything specific to Microsoft on this. this script does a fantastic job on fixing the paths if there's any so if you happen to have this issue, It'd be really handy (hats off to those who contributed to this project!) -

@Manoj Karunarathne 

How do you know if it succeeds. My vulnerability solution indicates the existence of the threat but does not specify the reg keys that are unquoted for the server KDSERVICE (Kyocera Printer Driver)