En bref
- CVE-2023-46733 est une vulnérabilité MOYENNE (CVSS 6.5) touchant symfony/security-http, symfony/symfony, symfony (sensiolabs).
- Probabilité d'exploitation dans les 30 prochains jours (EPSS) : 0.69%, plus élevée que 52.8% des vulnérabilités.
- Correctif : mettre à jour vers 5.4.31, 6.3.8 ou plus récent.
| Package | Affected versions | Patched versions |
|---|
| symfony/security-http Packagist | ≥ 5.4.21, < 5.4.31≥ 6.2.7, < 6.3.8
| 5.4.316.3.8
|
| symfony/symfony Packagist | ≥ 5.4.21, < 5.4.31≥ 6.2.7, < 6.3.8
| 5.4.316.3.8
|
| symfony | ≥ 5.4.21, < 5.4.31≥ 6.2.7, < 6.3.8
| 5.4.316.3.8
|
Description
Description
SessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.
Resolution
Symfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.
The patch for this issue is available here for branch 5.4.
Credits
We would like to thank Robert Meijers for reporting the issue and providing the fix.
NVD description
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Starting in versions 5.4.21 and 6.2.7 and prior to versions 5.4.31 and 6.3.8, `SessionStrategyListener` does not migrate the session after every successful login. It does so only in case the logged in user changes by means of checking the user identifier. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations, which is not the case at the moment. As of versions 5.4.31 and 6.3.8, Symfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.
Autres vulnérabilités de symfony/security-http
Tout voir →Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free