medium5.9
CVE-2017-16653
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.
Impact
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.
Affected products
| Vendor | Product | Affected versions |
|---|---|---|
| Sensiolabs | Symfony | from 2.7.0 through 2.7.37 from 3.2.0 through 3.2.13 from 3.3.0 through 3.3.12 from 3.8.0 through 3.8.30 |
| Debian | Debian Linux | Version 9.0 |
References
- NVD record
- CVE.org record
- https://github.com/symfony/symfony/pull/24992
- https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https
- https://www.debian.org/security/2018/dsa-4262
- https://github.com/symfony/symfony/pull/24992
- https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https
- https://www.debian.org/security/2018/dsa-4262