Symfony session fixiation

Summaryinfo

A vulnerability identified as critical has been detected in Symfony. This affects an unknown function. The manipulation leads to session fixiation. This vulnerability is uniquely identified as CVE-2023-46733. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Symfony (affected version not known) and classified as critical. This issue affects some unknown functionality. The manipulation with an unknown input leads to a session fixiation vulnerability. Using CWE to declare the problem leads to CWE-384. 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was disclosed 11/10/2023 as GHSA-m2wj-r6g3-fxfx. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2023-46733 since 10/25/2023. The technical details are unknown and an exploit is not publicly available.

Upgrading eliminates this vulnerability. Applying the patch 7467bd7e3f888b333102bc664b5e02ef1e7f88b9 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

• Symfony

License

• open-source

Website

• Product: https://github.com/symfony/symfony/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion