CVE-2017-16653Published Aug 6, 2018 · Aug 6Updated Oct 24
Symfony CSRF Vulnerability
Medium5.9Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/security-csrf Packagist |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| symfony/security-csrf Packagist |
|
|
| symfony/security Packagist |
|
|
| symfony/symfony Packagist |
|
|
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.
From the CVE record · mitre
Symfony’s CSRF protection uses the same token for HTTP and HTTPS. A network attacker who intercepts a token over HTTP can reuse it in an HTTPS context to carry out a CSRF attack.
Check applications using symfony/security-csrf, symfony/security, or symfony/symfony versions 2.7.0–2.7.37, 2.8.0–2.8.30, 3.0.0–3.2.13, or 3.3.0–3.3.12.