Cookie persistence in Symfony
symfony
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/security-bundle Packagist |
|
|
| symfony/symfony Packagist |
|
|
symfony
| Product | Affected | Fixed in |
|---|---|---|
| symfony/security-bundle Packagist |
|
|
| symfony/symfony Packagist |
|
|
Symfony/SecurityBundle is the security system for Symfony, a PHP framework for web and console applications and a set of reusable PHP components. Since the rework of the Remember me cookie in version 5.3.0, the cookie is not invalidated when the user changes their 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. Starting with version 5.3.12, Symfony makes the password part of the signature by default. In that way, when the password changes, then the cookie is not valid anymore.
From the CVE record · GitHub_M
In Symfony 5.3.0 through versions before 5.3.12, changing a password does not invalidate an existing Remember me cookie. An attacker who has previously logged in and obtained a valid cookie can retain access to the account after the password changes.
Teams running Packagist symfony/security-bundle or symfony/symfony versions >=5.3.0 and <5.3.12 should check their deployments.