Matching cookie names with an unanchored regular expression allows sibling subdomains or malicious actors to shadow cookies using prefixed cookie names (e.g., matching 'xname=' when searching for 'name='). Match cookie names with exact string equality or anchor with boundary delimiters such as '(?:^|;\\s*)'.
Rule Explorer
Search the public rule index by CVE, GHSA, CWE, language, framework, author, or rule slug. Filter by language, framework, severity, confidence, license, and validation status.
- Public rules
- 4797
- Downloads
- 12M
- Verified
- 4797
- Authors
- 2
Rack::Session::Cookie#unpacked_cookie_data falls back to an unauthenticated coder (e.g. Base64::Marshal) when configured encryptors fail to decrypt the cookie. Because encryptor failures are rescued and ignored, an attacker can forge a session cookie that fails authenticated decryption but is still parsed by the fallback coder, leading to authentication bypa
Writing arbitrary keys to the Django session dictionary from an external or dynamically generated dictionary without validation. This can lead to session mass-assignment, enabling an attacker to overwrite sensitive session variables such as user IDs or authentication credentials. Verify the source of the dictionary, and preferably set specific, statically st
A cookie is set via `send_header` without including the `SameSite` attribute. This lack of cross-origin restriction exposes the application to Cross-Site Request Forgery (CSRF) if the cookie handles sensitive session access. Add `SameSite=Lax` or `SameSite=Strict` to the cookie string to securely limit cross-origin exposure.