Symfony vulnerable to Session Fixation of CSRF tokens
symfony
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/security-bundle Packagist |
|
|
symfony
| Product | Affected | Fixed in |
|---|---|---|
| symfony/security-bundle Packagist |
|
|
6.1.126.2.6| symfony/symfony Packagist |
|
|
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. When authenticating users Symfony by default regenerates the session ID upon login, but preserves the rest of session attributes. Because this does not clear CSRF tokens upon login, this might enables same-site attackers to bypass the CSRF protection mechanism by performing an attack similar to a session-fixation. This issue has been fixed in the 4.4 branch.
From the CVE record · GitHub_M
Symfony regenerates the session ID at login but preserves session attributes, including CSRF tokens. A same-site attacker may use the retained tokens to bypass CSRF protection through an attack similar to session fixation when a user logs in.
Teams using Packagist symfony/security-bundle or symfony/symfony versions >=2.0.0 <4.4.50, >=5.0.0 <5.4.20, >=6.0.0 <6.0.20, >=6.1.0 <6.1.12, or >=6.2.0 <6.2.6 should check their installations.