Avoid unsafe Rails strong parameters and mass assignment
Strong parameters and mass assignment sinks should not accept unfiltered request hashes or privileged attributes.
#Metadata
#Why it matters
Permissive `permit!`, privileged `permit` fields, and direct `params` mass assignment enable attackers to escalate privileges or overwrite protected columns.
#Remediation
Replace `permit!` with an explicit attribute list, drop privileged symbols from `permit`, and route updates through vetted strong-parameter helpers instead of raw `params`.
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/ruby/ruby.security.rails-unsafe-strong-parameters.rule.yaml.