Commit 3a33192
committed
fix: regenerate CSRF token right after session regeneration
CSRF token is not updated when `security.regenerate = false`,
so if same-site attakcers know the CSRF token by session fixation attack,
CSRF attack is possible. To prevent it, regenerate CSRF token right after login.1 parent 47e08d2 commit 3a33192
1 file changed
Lines changed: 4 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
20 | 20 | | |
21 | 21 | | |
22 | 22 | | |
| 23 | + | |
23 | 24 | | |
24 | 25 | | |
25 | 26 | | |
| |||
568 | 569 | | |
569 | 570 | | |
570 | 571 | | |
| 572 | + | |
| 573 | + | |
| 574 | + | |
571 | 575 | | |
572 | 576 | | |
573 | 577 | | |
| |||
0 commit comments