Symfony CSRF Token Fixation
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/symfony Packagist |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| symfony/symfony Packagist |
|
|
3.4.114.0.11| symfony/security-bundle Packagist |
|
|
| symfony/security-http Packagist |
|
|
| symfony/security Packagist |
|
|
An issue was discovered in the Security component in Symfony 2.7.x before 2.7.48, 2.8.x before 2.8.41, 3.3.x before 3.3.17, 3.4.x before 3.4.11, and 4.0.x before 4.0.11. By default, a user's session is invalidated when the user is logged out. This behavior can be disabled through the invalidate_session option. In this case, CSRF tokens were not erased during logout which allowed for CSRF token fixation.
From the CVE record · mitre
Symfony's Security component did not erase CSRF tokens on logout when the invalidate_session option was disabled. This allowed CSRF token fixation; the input does not specify whether authentication or user interaction is required.
Check applications using symfony/symfony, symfony/security-bundle, symfony/security-http, or symfony/security in affected 2.7.x, 2.8.x, 3.0–3.3.x, 3.4.x, or 4.0.x ranges.