GHSA-92x6-h2gr-8gxq Symfony CSRF Vulnerability

• Packagist symfony/security-csrf: >= 2.7.0, < 2.7.38 → fixed in 2.7.38 • Packagist symfony/security-csrf: >= 2.8.0, < 2.8.31 → fixed in 2.8.31 • Packagist symfony/security-csrf: >= 3.0.0, < 3.2.14 → fixed in 3.2.14 • Packagist symfony/security-csrf: >= 3.3.0, < 3.3.13 → fixed in 3.3.13 • Packagist symfony/security: >= 2.7.0, < 2.7.38 → fixed in 2.7.38 • Packagist symfony/security: >= 2.8.0, < 2.8.31 → fixed in 2.8.31 • Packagist symfony/security: >= 3.0.0, < 3.2.14 → fixed in 3.2.14 • Packagist symfony/security: >= 3.3.0, < 3.3.13 → fixed in 3.3.13 • Packagist symfony/symfony: >= 2.7.0, < 2.7.38 → fixed in 2.7.38 • Packagist symfony/symfony: >= 2.8.0, < 2.8.31 → fixed in 2.8.31 • Packagist symfony/symfony: >= 3.0.0, < 3.2.14 → fixed in 3.2.14 • Packagist symfony/symfony: >= 3.3.0, < 3.3.13 → fixed in 3.3.13

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.