HighGHSA-g4g7-q726-v5hgCVE-2018-11406
Symfony CSRF Token Fixation
Published 14 May 2022 · Updated 18 Feb 2024
Affected packages
symfony/symfonyComposer
- Affected
- >=2.7.0 <2.7.48
- Fixed in
- 2.7.48
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^2.7.48symfony/symfonyComposer
- Affected
- >=2.8.0 <2.8.41
- Fixed in
- 2.8.41
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^2.8.41symfony/symfonyComposer
- Affected
- >=3.0.0 <3.3.17
- Fixed in
- 3.3.17
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^3.3.17symfony/symfonyComposer
- Affected
- >=3.4.0 <3.4.11
- Fixed in
- 3.4.11
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^3.4.11symfony/symfonyComposer
- Affected
- >=4.0.0 <4.0.11
- Fixed in
- 4.0.11
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^4.0.11symfony/security-bundleComposer
- Affected
- >=2.7.0 <2.7.48
- Fixed in
- 2.7.48
Update to the fixed version for your release line, for example:
composer require symfony/security-bundle:^2.7.48symfony/security-bundleComposer
- Affected
- >=2.8.0 <2.8.41
- Fixed in
- 2.8.41
Update to the fixed version for your release line, for example:
composer require symfony/security-bundle:^2.8.41symfony/security-bundleComposer
- Affected
- >=3.0.0 <3.3.17
- Fixed in
- 3.3.17
Update to the fixed version for your release line, for example:
composer require symfony/security-bundle:^3.3.17symfony/security-bundleComposer
- Affected
- >=3.4.0 <3.4.11
- Fixed in
- 3.4.11
Update to the fixed version for your release line, for example:
composer require symfony/security-bundle:^3.4.11symfony/security-bundleComposer
- Affected
- >=4.0.0 <4.0.11
- Fixed in
- 4.0.11
Update to the fixed version for your release line, for example:
composer require symfony/security-bundle:^4.0.11symfony/security-httpComposer
- Affected
- >=2.7.0 <2.7.48
- Fixed in
- 2.7.48
Update to the fixed version for your release line, for example:
composer require symfony/security-http:^2.7.48symfony/security-httpComposer
- Affected
- >=2.8.0 <2.8.41
- Fixed in
- 2.8.41
Update to the fixed version for your release line, for example:
composer require symfony/security-http:^2.8.41symfony/security-httpComposer
- Affected
- >=3.0.0 <3.3.17
- Fixed in
- 3.3.17
Update to the fixed version for your release line, for example:
composer require symfony/security-http:^3.3.17symfony/security-httpComposer
- Affected
- >=3.4.0 <3.4.11
- Fixed in
- 3.4.11
Update to the fixed version for your release line, for example:
composer require symfony/security-http:^3.4.11symfony/security-httpComposer
- Affected
- >=4.0.0 <4.0.11
- Fixed in
- 4.0.11
Update to the fixed version for your release line, for example:
composer require symfony/security-http:^4.0.11symfony/securityComposer
- Affected
- >=2.7.0 <2.7.48
- Fixed in
- 2.7.48
Update to the fixed version for your release line, for example:
composer require symfony/security:^2.7.48symfony/securityComposer
- Affected
- >=2.8.0 <2.8.41
- Fixed in
- 2.8.41
Update to the fixed version for your release line, for example:
composer require symfony/security:^2.8.41symfony/securityComposer
- Affected
- >=3.0.0 <3.3.17
- Fixed in
- 3.3.17
Update to the fixed version for your release line, for example:
composer require symfony/security:^3.3.17symfony/securityComposer
- Affected
- >=3.4.0 <3.4.11
- Fixed in
- 3.4.11
Update to the fixed version for your release line, for example:
composer require symfony/security:^3.4.11symfony/securityComposer
- Affected
- >=4.0.0 <4.0.11
- Fixed in
- 4.0.11
Update to the fixed version for your release line, for example:
composer require symfony/security:^4.0.11Details
An issue was discovered in the Security component in Symfony 2.7.x before 2.7.48, 2.8.x before 2.8.41, 3.3.x before 3.3.17, 3.4.x before 3.4.11, and 4.0.x before 4.0.11. By default, a user's session is invalidated when the user is logged out. This behavior can be disabled through the invalidate_session option. In this case, CSRF tokens were not erased during logout which allowed for CSRF token fixation.
Is GHSA-g4g7-q726-v5hg in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected symfony/symfony, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2018-11406
- Linkgithub.com/symfony/symfony/commit/319e1bdd43979d9c1559497de8d69adea28ab8d1
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/security-bundle/CVE-2018-11406.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/security-http/CVE-2018-11406.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/security/CVE-2018-11406.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2018-11406.yaml
- Packagegithub.com/symfony/symfony
- Linklists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/G4XNBMFW33H47O5TZGA7JYCVLDBCXAJV
- Linklists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UBQK7JDXIELADIPGZIOUCZKMAJM5LSBW
- Linklists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WU5N2TZFNGXDGMXMPP7LZCWTFLENF6WH
- Linksymfony.com/blog/cve-2018-11406-csrf-token-fixation
- Linksymfony.com/cve-2018-11406
- Linkwww.debian.org/security/2018/dsa-4262
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.