Session Fixation
CVE-2023-46733
Summary
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. In versions 5.4.21 through 5.4.30, 6.2.7 through 6.3.7, 6.4.0-BETA1 through 6.4.0-BETA2, and 7.0.0-BETA1 through 7.0.0-BETA2 `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. In the fixed versions, Symfony now checks the type of the token in addition to the user identifier before deciding whether the session ID should be regenerated.
- LOW
- NETWORK
- HIGH
- UNCHANGED
- NONE
- LOW
- NONE
- NONE
CWE-384 - Session Fixation
Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
References
Advisory Timeline
- Published