Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unquoted service path #657

Closed
M507 opened this issue Sep 1, 2020 · 3 comments
Closed

Unquoted service path #657

M507 opened this issue Sep 1, 2020 · 3 comments

Comments

@M507
Copy link

M507 commented Sep 1, 2020

Hi Veyon team,

After installing Veyon v4.4.1, I noticed that its service, "VeyonService", is hijackable due to the unquoted service path. Using this vulnerability, attackers can execute different files as VeyonService. It allows local users to replace the service with arbitrary code to escalate their privileges. I hope you check this link for more details: https://cwe.mitre.org/data/definitions/428.html

@tobydox tobydox closed this as completed in f231ec5 Sep 1, 2020
@tobydox
Copy link
Contributor

tobydox commented Sep 1, 2020

Thank you very much for your bug report and sharing your findings! The issue has been fixed via f231ec5 and will be fixed in the upcoming 4.4.2 release.

tobydox added a commit that referenced this issue Sep 1, 2020
Fix unquoted service path vulnerability.

Closes #657.

(cherry picked from commit f231ec5)
@takito1812
Copy link

takito1812 commented Jun 1, 2021

Hello,

This issue was discovered by me months before, specifically at the end of March 2020.
The exploit is available at https://www.exploit-db.com/exploits/48246 and https://www.exploit-db.com/exploits/49925.
Hope it is possible to update the References in the Security Advisories and in the CVE.

Thanks.

@M507
Copy link
Author

M507 commented Jun 1, 2021

Hi @takito1812
I understand the reason behind this request. This is an easy-to-spot vulnerability, and it appears that two people found it on different versions. Good job on finding it, too 👍. Next time when you find a vulnerability in software, I recommend that you start by reporting the bug to the developers. Fixing the bug should be your first concern, not dropping a POC on Exploit-DB. When you get no replies, then I would say yes, post it on Exploit-DB to claim the work. Regarding the CVE "authorship", you can also claim it; I don't mind that. Happy hunting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants