Do not store raw request params in session or cookies
Session and signed cookie stores should not persist raw `params` blobs that attackers can influence.
#Metadata
#Why it matters
Writing `params` directly into `session` or `cookies` enables tampering, fixation, and oversized payload attacks unless additional integrity controls exist.
#Remediation
Store opaque identifiers, use signed or encrypted cookie jars appropriately, and validate any user-derived values before persistence.
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/ruby/ruby.security.rails-unsafe-session-or-cookie-store.rule.yaml.