| Package | Affected versions | Patched versions |
|---|---|---|
| symfony/security | ≥ 2.7.0, < 2.7.38≥ 2.8.0, < 2.8.31≥ 3.0.0, < 3.2.14≥ 3.3.0, < 3.3.13 | 2.7.382.8.313.2.143.3.13 |
| symfony/security-csrf | ≥ 2.7.0, < 2.7.38≥ 2.8.0, < 2.8.31≥ 3.0.0, < 3.2.14≥ 3.3.0, < 3.3.13 | 2.7.382.8.313.2.143.3.13 |
| symfony/symfony | ≥ 2.7.0, < 2.7.38≥ 2.8.0, < 2.8.31≥ 3.0.0, < 3.2.14≥ 3.3.0, < 3.3.13 | 2.7.382.8.313.2.143.3.13 |
| symfony | ≥ 2.7.0, ≤ 2.7.37≥ 3.2.0, ≤ 3.2.13≥ 3.3.0, ≤ 3.3.12≥ 3.8.0, ≤ 3.8.30 |
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free