You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 17, 2017. It is now read-only.
tainted information will not be passed when params[:user].symbolize_keys or params.to_hash (any method that may change the type) is called, because only ActionController::Parameters has permitted? method. So developers can easily accidentally bypass this strong parameter protection. Did strong parameter consider this?
The text was updated successfully, but these errors were encountered:
OrlandoLee
changed the title
developers can easily bypass mass assignment protection
developers can easily bypass mass assignment protection without noticing
Aug 15, 2014
Hey @OrlandoLee. This is a compatibility gem for Rails versions prior to 4. Perhaps you should submit an issue against rails/rails to see if they consider this to be a security issue.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
tainted information will not be passed when params[:user].symbolize_keys or params.to_hash (any method that may change the type) is called, because only ActionController::Parameters has permitted? method. So developers can easily accidentally bypass this strong parameter protection. Did strong parameter consider this?
The text was updated successfully, but these errors were encountered: