solidus_auth_devise
Affected
- introduced
1.0.0, fixed2.5.4(ecosystem)
Fixed versions
2.5.4
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2021-41274
Authentication Bypass by CSRF Weakness
Impact
CSRF vulnerability that allows user account takeover.
All applications using any version of the frontend component of solidus_auth_devise are affected if protect_from_forgery method is both:
before_action callback (the default)prepend_before_action (option prepend: true given) before the :load_object hook in Spree::UserController (most likely order to find).:null_session or :reset_session strategies (:null_session is the default in case the no strategy is given, but rails --new generated skeleton use :exception).That means that applications that haven't been configured differently from what it's generated with Rails aren't affected.
Patches
Users should promptly update to solidus_auth_devise version 2.5.4.
Workarounds
A couple of options:
:exception: class ApplicationController < ActionController::Base
protect_from_forgery with: :exception
end
config/application.rb to at least run the :exception strategy on the affected controller: config.after_initialize do
Spree::UsersController.protect_from_forgery with: :exception
end
solidus_auth_devise with the quick fix. Those versions are v3.1.3, v.3.0.3 & v2.11.12. See GHSA-5629-8855-gf4g for details.References
Thanks
We'd like to thank vampire000 for reporting this issue.
For more information
If you have any questions or comments about this advisory:
Critical Basis: The source's own band: CRITICAL
1.0.0, fixed 2.5.4 (ecosystem)2.5.4
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0