| Package | Affected versions | Patched versions |
|---|---|---|
| symfony/security | ≥ 2.7.0, < 2.7.48≥ 2.8.0, < 2.8.41≥ 3.0.0, < 3.3.17≥ 3.4.0, < 3.4.11≥ 4.0.0, < 4.0.11 | 2.7.482.8.413.3.173.4.114.0.11 |
| symfony/security-bundle | ≥ 2.7.0, < 2.7.48≥ 2.8.0, < 2.8.41≥ 3.0.0, < 3.3.17≥ 3.4.0, < 3.4.11≥ 4.0.0, < 4.0.11 | 2.7.482.8.413.3.173.4.114.0.11 |
| symfony/security-http | ≥ 2.7.0, < 2.7.48≥ 2.8.0, < 2.8.41≥ 3.0.0, < 3.3.17≥ 3.4.0, < 3.4.11≥ 4.0.0, < 4.0.11 | 2.7.482.8.413.3.173.4.114.0.11 |
| symfony/symfony | ≥ 2.7.0, < 2.7.48≥ 2.8.0, < 2.8.41≥ 3.0.0, < 3.3.17≥ 3.4.0, < 3.4.11≥ 4.0.0, < 4.0.11 | 2.7.482.8.413.3.173.4.114.0.11 |
| symfony | ≥ 2.7.0, < 2.7.48≥ 2.8.0, < 2.8.41≥ 3.3.0, < 3.3.17≥ 3.4.0, < 3.4.11≥ 4.0.0, < 4.0.11 | 2.7.482.8.413.3.173.4.114.0.11 |
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free