GoogleOSV:GHSA-92X6-H2GR-8GXQSymfony CSRF Vulnerability
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.
References
github.com/FriendsOfPHP/security-advisories/blob/master/symfony/security-csrf/CVE-2017-16653.yaml
github.com/FriendsOfPHP/security-advisories/blob/master/symfony/security/CVE-2017-16653.yaml
github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2017-16653.yaml
github.com/symfony/symfony
github.com/symfony/symfony/commit/b4dbdd7cd8732483d585eacff3428c16b07ad15e
github.com/symfony/symfony/pull/24992
nvd.nist.gov/vuln/detail/CVE-2017-16653
symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https
symfony.com/cve-2017-16653
www.debian.org/security/2018/dsa-4262
Related
