Skip to content

Symfony vulnerable to Session Fixation of CSRF tokens

Moderate severity GitHub Reviewed Published Feb 1, 2023 in symfony/symfony • Updated Jul 12, 2023

Package

composer symfony/security-bundle (Composer)

Affected versions

>= 2.0.0, < 4.4.50
>= 5.0.0, < 5.4.20
>= 6.0.0, < 6.0.20
>= 6.1.0, < 6.1.12
>= 6.2.0, < 6.2.6

Patched versions

4.4.50
5.4.20
6.0.20
6.1.12
6.2.6
composer symfony/symfony (Composer)
>= 2.0.0, < 4.4.50
>= 5.0.0, < 5.4.20
>= 6.0.0, < 6.0.20
>= 6.1.0, < 6.1.12
>= 6.2.0, < 6.2.6
4.4.50
5.4.20
6.0.20
6.1.12
6.2.6

Description

Description

When authenticating users Symfony by default regenerates the session ID upon login, but preserves the rest of session attributes. Because this does not clear CSRF tokens upon login, this might enables same-site attackers to bypass the CSRF protection mechanism by performing an attack similar to a session-fixation.

Resolution

Symfony removes all CSRF tokens from the session on successful login.

The patch for this issue is available here for branch 4.4.

Credits

We would like to thank Marco Squarcina for reporting the issue and Nicolas Grekas for fixing it.

References

@fabpot fabpot published to symfony/symfony Feb 1, 2023
Published to the GitHub Advisory Database Feb 1, 2023
Reviewed Feb 1, 2023
Published by the National Vulnerability Database Feb 3, 2023
Last updated Jul 12, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

EPSS score

0.234%
(61st percentile)

Weaknesses

CVE ID

CVE-2022-24895

GHSA ID

GHSA-3gv2-29qc-v67m

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.