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.
| Package (Ecosystem) | Introduced | Fixed | Limit |
|---|---|---|---|
| symfony/security-csrf(Packagist) | 2.7.0 | 2.7.38 | N/A |
| symfony/security-csrf(Packagist) | 2.8.0 | 2.8.31 | N/A |
| symfony/security-csrf(Packagist) | 3.0.0 | 3.2.14 | N/A |
| symfony/security-csrf(Packagist) | 3.3.0 | 3.3.13 | N/A |
| symfony/security(Packagist) | 2.7.0 | 2.7.38 | N/A |
| symfony/security(Packagist) | 2.8.0 | 2.8.31 | N/A |
| symfony/security(Packagist) | 3.0.0 | 3.2.14 | N/A |
| symfony/security(Packagist) | 3.3.0 | 3.3.13 | N/A |
| symfony/symfony(Packagist) | 2.7.0 | 2.7.38 | N/A |
| symfony/symfony(Packagist) | 2.8.0 | 2.8.31 | N/A |
| symfony/symfony(Packagist) | 3.0.0 | 3.2.14 | N/A |
| symfony/symfony(Packagist) | 3.3.0 | 3.3.13 | N/A |
CVSS Metrics
