yesod/yesod-auth/Yesod/Auth
Sibi Prabakaran 7f17d829b3
Fix CSRF security vulnerability in registerHelper function
Return a 403 status code if the csrf tokens are matched. This currently
affects two endpoints: During registration and during password reset
forms.

This curl request demonstrates how this can be exploited to register new
email:

curl -i --header "Accept: application/json" --request POST -F
"email=sibi@psibi.in" http://localhost:3005/auth/page/email/register

With the patch applied, it will respond with this:

{"message":"Permission Denied. A valid CSRF token wasn't present in HTTP
headers or POST parameters. Because the request could have been forged,
it's been rejected altogether. Check the Yesod.Core.Handler docs of the
yesod-core package for details on CSRF protection."}
2016-11-20 03:59:32 +05:30
..
BrowserId.hs Deprecate BrowserId #1173 2016-03-08 16:27:21 +02:00
Dummy.hs Provide CSRF token in Dummy login form 2016-04-02 23:04:58 -04:00
Email.hs Fix CSRF security vulnerability in registerHelper function 2016-11-20 03:59:32 +05:30
GoogleEmail2.hs Comment on unsafePerformIO, close #1245 2016-10-03 09:08:22 -07:00
GoogleEmail.hs Deprecate Yesod.Auth.GoogleEmail #1150 2016-01-21 09:00:50 +02:00
Hardcoded.hs Use defaultCsrfParamName instead of hard-coding its value 2016-02-15 23:59:24 -08:00
Message.hs Translation bug in german message 2016-09-01 11:55:44 +02:00
OpenId.hs Remove redundant imports 2015-06-24 20:54:27 +05:00
Routes.hs Added missing pragma 2014-09-08 07:11:38 +03:00
Rpxnow.hs Remove redundant imports 2015-06-24 20:54:27 +05:00