CODEWITHSUNDEEP
laravelcookiescsrf
cr001
cr001

Reputation: 663

How is Laravel 8 CSRF token actually safe?

The most voted answer in this question (https://security.stackexchange.com/questions/19128/csrf-cookie-vs-session-based-tokens) states

If you put your token in a cookie, it will be send to the server automatically, just as session cookie, so you don't get any additional protection from that.

And Laravel seems to behave exactly as stated above. Here's the screenshot I have tested.

enter image description here

I am not sure whether I am doing some settings wrong or misunderstood about CSRF, but storing an extra CSRF cookie in addition to the session cookie really does not seem to be able to give any extra protection.

Any help would be appreciated.

Upvotes: 0

Views: 1518

Answers (1)

Parsa_Gholipour
Parsa_Gholipour

Reputation: 960

Not always. cookie with SameSite value of None will be always sent. XSRF-TOKEN cookie has SameSite=Lax so it will be only sent at the same website.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite#none

SameSite=None Cookies will be sent in all contexts, i.e. in responses to both first-party and cross-site requests. If SameSite=None is set, the cookie Secure attribute must also be set (or the cookie will be blocked).

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite#lax

SameSite=Lax Cookies are not sent on normal cross-site subrequests (for example to load images or frames into a third party site), but are sent when a user is navigating to the origin site (i.e., when following a link).

Upvotes: 1

Related Questions