Skip to content

Cookie persistence after password changes in symfony/security-bundle

Moderate severity GitHub Reviewed Published Nov 24, 2021 in symfony/symfony • Updated Feb 5, 2024

Package

composer symfony/security-bundle (Composer)

Affected versions

>= 5.3.0, < 5.3.12

Patched versions

5.3.12
composer symfony/symfony (Composer)
>= 5.3.0, < 5.3.12
5.3.12

Description

Description

Since the rework of the Remember me cookie in Symfony 5.3, the cookie is not invalidated anymore when the user changes its password.

Attackers can therefore maintain their access to the account even if the password is changed as long as they have had the chance to login once and get a valid remember me cookie.

Resolution

Symfony now makes the password part of the signature by default. In that way, when the password changes then the cookie is not valid anymore.

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

Credits

We would like to thank Thibaut Decherit for reporting the issue and Wouter J for fixing the issue.

References

@fabpot fabpot published to symfony/symfony Nov 24, 2021
Published by the National Vulnerability Database Nov 24, 2021
Reviewed Nov 24, 2021
Published to the GitHub Advisory Database Nov 24, 2021
Last updated Feb 5, 2024

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.133%
(50th percentile)

Weaknesses

CVE ID

CVE-2021-41268

GHSA ID

GHSA-qw36-p97w-vcqr

Source code

Credits

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