-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Open Redirection Vulnerability #268
Comments
Added caddy-security/caddyfile_authn_misc.go Lines 70 to 110 in 90049c8
That, in turn, enables the verification of the redirect url.
|
@greenpau I tried adding |
@binarious, thank you for testing the directive. please reach out to me on Linkedin. Will troubleshoot over Google Meet. Also, please open another issue for this and reference this one. |
When a logged-in user clicks on a specially crafted link with a
redirect_url
parameter, the user can be redirected to an external website. The user must take an action, such as clicking on a portal button or using the browser’s back button, to trigger the redirection. This could lead to phishing attacks, where an attacker tricks users into visiting a malicious website by crafting a convincing URL.When logged-in, a victim clicks on the link: https://portal.caddysecurity.network/auth/whoami?redirect_url=https://nvmgpc54pak47d02e6a1l6c6wx2oqfo3d.oastify.com
Then, he clicks on the
Portal
button. He is redirected to the redirect_url through this request:When he uses arrows in the browser to come back to the authorization process, he can be redirected to the external domain by this request too:
To mitigate this vulnerability, perform proper redirect_url parameter validation to ensure that the redirection URLs are allowed only within the same domain or from trusted sources.
In addition, we also recommend the following long-term fixes:
More information about our Caddy Security public disclosure:
The text was updated successfully, but these errors were encountered: