Skip to content

Commit e4a2ac2

Browse files
fa11enangelrwinch
authored andcommitted
Fixed link to CSRF checks
1 parent 401f836 commit e4a2ac2

File tree

1 file changed

+1
-1
lines changed
  • docs/modules/ROOT/pages/features/exploits

1 file changed

+1
-1
lines changed

docs/modules/ROOT/pages/features/exploits/csrf.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -324,7 +324,7 @@ This lets the expected CSRF token outlive the session.
324324
+
325325
One might ask why the expected CSRF token is not stored in a cookie by default.
326326
This is because there are known exploits in which headers (for example, to specify the cookies) can be set by another domain.
327-
This is the same reason Ruby on Rails https://weblog.rubyonrails.org/2011/2/8/csrf-protection-bypass-in-ruby-on-rails/[no longer skips a CSRF checks when the header X-Requested-With is present].
327+
This is the same reason Ruby on Rails https://rubyonrails.org/2011/2/8/csrf-protection-bypass-in-ruby-on-rails[no longer skips a CSRF checks when the header X-Requested-With is present].
328328
See https://web.archive.org/web/20210221120355/https://lists.webappsec.org/pipermail/websecurity_lists.webappsec.org/2011-February/007533.html[this webappsec.org thread] for details on how to perform the exploit.
329329
Another disadvantage is that by removing the state (that is, the timeout), you lose the ability to forcibly invalidate the token if it is compromised.
330330

0 commit comments

Comments
 (0)