Timeline for CSRF Token in GET request
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 14, 2017 at 14:49 | comment | added | Amit | @LucasKauffman I can't find a reference of "CSRF token should not be contained withing a GET request" can you please share if you have any OWASP reference for this ? | |
| Aug 31, 2016 at 8:10 | answer | added | SilverlightFox | timeline score: 10 | |
| May 31, 2013 at 9:13 | answer | added | bobince | timeline score: 5 | |
| May 30, 2013 at 20:07 | history | tweeted | twitter.com/#!/StackSecurity/status/340197861046251521 | ||
| May 30, 2013 at 13:35 | vote | accept | Lucas Kauffman | ||
| May 30, 2013 at 13:34 | answer | added | Adi | timeline score: 15 | |
| May 30, 2013 at 12:19 | comment | added | Lucas Kauffman | I just wanted some kind of confirmation | |
| May 30, 2013 at 11:50 | answer | added | Luc | timeline score: 3 | |
| May 30, 2013 at 11:43 | comment | added | Adi | If you're generating the tokens in a secure random fashion, then an attacker cannot infer the next token from the previous ones. So there shouldn't be any realistic risk. It feels weird telling you that. | |
| May 30, 2013 at 11:33 | history | asked | Lucas Kauffman | CC BY-SA 3.0 |