-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
"Covert Redirect" Vulnerability #696
Comments
I've used |
@prshreshtha - playing catch up. did you close this because you decided this was invalid? |
No. But you can avoid it by having your own controller. By default, this is still an issue. I think at the very least, the docs should mention it. Personally, I think whitelisting should be in the configuration. I'm not sure why I had closed the issue. It was probably an error on my part, sorry. |
Does the https://github.com/lynndylanhurley/devise_token_auth#configuration-cont |
|
@prshreshtha - does #699 resolve the issue? |
👍 |
@prshreshtha - thanks for bringing this up. @booleanbetrayal - we may want to cut a release to patch this vulnerability. what do you think? |
sounds good ... just merged the fix |
@lynndylanhurley / @prshreshtha - just built and pushed v0.1.39 |
Thanks @booleanbetrayal!! |
@lynndylanhurley @booleanbetrayal
I can't seem to find a way to whitelist values for
auth_origin_url
used here.Here's a quick description
Something like this is currently possible:
http://localhost:3000/auth/:provider/?origin=https://evil.com/capture-access-token
Other than writing my own controller, what is the solution?
The text was updated successfully, but these errors were encountered: