MediumGHSA-92x6-h2gr-8gxqCVE-2017-16653
Symfony CSRF Vulnerability
Published 13 May 2022 · Updated 16 Feb 2024
Affected packages
symfony/security-csrfComposer
- Affected
- >=2.7.0 <2.7.38
- Fixed in
- 2.7.38
Update to the fixed version for your release line, for example:
composer require symfony/security-csrf:^2.7.38symfony/security-csrfComposer
- Affected
- >=2.8.0 <2.8.31
- Fixed in
- 2.8.31
Update to the fixed version for your release line, for example:
composer require symfony/security-csrf:^2.8.31symfony/security-csrfComposer
- Affected
- >=3.0.0 <3.2.14
- Fixed in
- 3.2.14
Update to the fixed version for your release line, for example:
composer require symfony/security-csrf:^3.2.14symfony/security-csrfComposer
- Affected
- >=3.3.0 <3.3.13
- Fixed in
- 3.3.13
Update to the fixed version for your release line, for example:
composer require symfony/security-csrf:^3.3.13symfony/securityComposer
- Affected
- >=2.7.0 <2.7.38
- Fixed in
- 2.7.38
Update to the fixed version for your release line, for example:
composer require symfony/security:^2.7.38symfony/securityComposer
- Affected
- >=2.8.0 <2.8.31
- Fixed in
- 2.8.31
Update to the fixed version for your release line, for example:
composer require symfony/security:^2.8.31symfony/securityComposer
- Affected
- >=3.0.0 <3.2.14
- Fixed in
- 3.2.14
Update to the fixed version for your release line, for example:
composer require symfony/security:^3.2.14symfony/securityComposer
- Affected
- >=3.3.0 <3.3.13
- Fixed in
- 3.3.13
Update to the fixed version for your release line, for example:
composer require symfony/security:^3.3.13symfony/symfonyComposer
- Affected
- >=2.7.0 <2.7.38
- Fixed in
- 2.7.38
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^2.7.38symfony/symfonyComposer
- Affected
- >=2.8.0 <2.8.31
- Fixed in
- 2.8.31
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^2.8.31symfony/symfonyComposer
- Affected
- >=3.0.0 <3.2.14
- Fixed in
- 3.2.14
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^3.2.14symfony/symfonyComposer
- Affected
- >=3.3.0 <3.3.13
- Fixed in
- 3.3.13
Update to the fixed version for your release line, for example:
composer require symfony/symfony:^3.3.13Details
An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.
Is GHSA-92x6-h2gr-8gxq 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/security-csrf, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2017-16653
- Linkgithub.com/symfony/symfony/pull/24992
- Linkgithub.com/symfony/symfony/commit/b4dbdd7cd8732483d585eacff3428c16b07ad15e
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/security-csrf/CVE-2017-16653.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/security/CVE-2017-16653.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2017-16653.yaml
- Packagegithub.com/symfony/symfony
- Linksymfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https
- Linksymfony.com/cve-2017-16653
- Linkwww.debian.org/security/2018/dsa-4262
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.