Devise has been reported to be vulnerable to CSRF token fixation attacks.
The attack can only be exploited if the attacker can set the target session, either by subdomain cookies (similar to described here) or by fixation over the same Wi-Fi network. If the user knows the CSRF token, cross-site forgery requests can be made. More information can be found here.
Note Devise is not vulnerable to session fixation attacks (i.e. the user cannot steal another user session by fixating the session id).
Devise 3.0.1 and 2.2.5 have been released with fixes for the attack.
If you can’t upgrade, you must protect your Devise application by adding the next three lines to a Rails initializer:
Warden::Manager.after_authentication do |record, warden, options| warden.request.session.try(:delete, :_csrf_token) end
Notice the code above and the updated Devise versions will clean up the CSRF Token after any authentication (sign in, sign up, reset password, etc). So if you are using AJAX for such features, you will need to fetch a new CSRF token from the server.
We want to thank Egor Homakov for reporting the issue and working with us on a fix.
English. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.