[Vulnerability] Cross site scripting (XSS) and Open Redirect on the login page #396
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The login page is vulnerable to open redirect and XSS attacks. An attacker can craft a seemingly valid URL and then trick the admin into clicking, after the admin authenticates the payload will run, which will :
a. Create a new webui user with admin privileges, which can be used to takeover the entire application.
b. Create new clients, exfiltrate existing client config and send to attacker. This can lead to exposure of private network/servers, enabling further exploitation.
Cause
The function redirectNext in login.html does not check the value of 'next' parameters before redirecting:
Steps to reproduce
Login URL: https://example.com:5000/login?next=/
Change the 'next' parameter to any url:
https://example.com:5000/login?next=https://malicious.domain
After logging in the user will be redirected to the malicious domain.
Change the 'next' parameter to:
Screenshot
The fix
Check if the 'next' param is just a singular slash (/) or starts with a slash and a character. This will prevent payloads like these: