Cookie Flags
General
SameSite
None
Sends the cookie everywhere. Some browsers will block a cookie with this settings if the Secure
flag is not set.
Lax
Doesn't send the cookie on cross-site requests. It will only send it when a user manually enters the URL in the browser or clicks a link to the site.
Strict
Sends the cookie only on same-origin requests.
Attack Scenario
A malicious attacker-controlled domain can trick an authenticated user into issuing cross-origin requests to a legitimate target site; with the session cookie set to SameSite=None
, the browser automatically includes it, enabling CSRF attacks even though the HttpOnly
attribute prevents client-side access.
Recommendations
Configure session cookies with SameSite=Lax
or Strict
where possible; if SameSite=None
is required, implement comprehensive server-side CSRF mitigations, including per-request tokens and strict Origin/Referer validation, while maintaining Secure
and HttpOnly
attributes.
Resources
Last updated
Was this helpful?