[GH-ISSUE #1219] Unquoted service path on windows #981

New issue

Open

opened 2026-05-05 07:21:06 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 07:21:06 -06:00

Owner

Originally created by @petecog on GitHub (Jul 1, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1219

Describe the bug
I've noticed that the service path created in windows registry is unquoted - which can cause a vulnerability. see https://medium.com/@SumitVerma101/windows-privilege-escalation-part-1-unquoted-service-path-c7a011a8d8ae for example

To Reproduce

Steps to reproduce the behavior:

install v2.3.3
Inspect HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Barrier\ImagePath

Expected behavior
Ideally value should be quoted e.g. "C:\Program Files\Barrier\barrierd.exe" - becuse of the space in 'Program Files'

Desktop (please complete the following information):

OS: Windows 10
Barrier version: 2.3.3

Originally created by @petecog on GitHub (Jul 1, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1219 **Describe the bug** I've noticed that the service path created in windows registry is unquoted - which can cause a vulnerability. see https://medium.com/@SumitVerma101/windows-privilege-escalation-part-1-unquoted-service-path-c7a011a8d8ae for example **To Reproduce** Steps to reproduce the behavior: 1. install v2.3.3 2. Inspect HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Barrier\ImagePath **Expected behavior** Ideally value should be quoted e.g. "C:\Program Files\Barrier\barrierd.exe" - becuse of the space in 'Program Files' **Desktop (please complete the following information):** - OS: Windows 10 - Barrier version: 2.3.3

gitea-mirror commented

2026-05-05 07:21:09 -06:00

Author

Owner

@shymega commented on GitHub (Jul 6, 2021):

Hi. Thanks for the report. Given this is a serious security vulnerability, perhaps it should be reported to an email address to me and the other devs directly - but that's not set up yet. I'll look into that... we have another report as well, so obviously we have some vulns that need looking into. Rest assured, we are looking into this - I'll keep the issue open for now.

Thanks again!

@shymega commented on GitHub (Jul 6, 2021): Hi. Thanks for the report. Given this is a serious security vulnerability, perhaps it should be reported to an email address to me and the other devs directly - but that's not set up yet. I'll look into that... we have another report as well, so obviously we have some vulns that need looking into. Rest assured, we are looking into this - I'll keep the issue open for now. Thanks again!

gitea-mirror commented

2026-05-05 07:21:10 -06:00

Author

Owner

@starmaid commented on GitHub (Mar 11, 2022):

bumping this, still an issue in 2.4.0 and nessus keeps flagging it

@starmaid commented on GitHub (Mar 11, 2022): bumping this, still an issue in 2.4.0 and nessus keeps flagging it