-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Logic bug regarding spinner-based protection #133
Comments
Hello @se2342, I think that makes sense, I can't remember now a valid reason to not have this extra check in place. |
Hello again @se2342, I just pushed this change in #134. I'll cut a new release to RubyGems soon: v2.2.0...master |
UPDATE I finally released a new version now 🚀 https://rubygems.org/gems/invisible_captcha/versions/2.3.0 |
Awesome. Thank you for your work as a maintainer. 👏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behaviour
When setting
spinner_enabled = true
requests with an emptyparams[:spinner]
should fail regardless of whether the client has requested a view that invokesinvisible_captcha
form helper.Actual Behaviour
When
spinner_enabled = true
is set but no previous Rails view has been called,session[:invisible_captcha_spinner]
is empty thus not making validparams[:spinner]
a prerequisite for the request to be executed i.e. malicious requests are not detected as spam, effectively bypassing the spinner-based protection.See
invisible_captcha/lib/invisible_captcha/controller_ext.rb
Line 78 in fc5dd70
Proposal
Improve conditional logic as follows:
The text was updated successfully, but these errors were encountered: