Vulnerability Description
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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Sensiolabs | Symfony | >= 2.7.0, <= 2.7.37 |
| Debian | Debian Linux | 9.0 |
References
- https://github.com/symfony/symfony/pull/24992Issue TrackingThird Party Advisory
- https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tIssue TrackingThird Party Advisory
- https://www.debian.org/security/2018/dsa-4262Third Party Advisory
- https://github.com/symfony/symfony/pull/24992Issue TrackingThird Party Advisory
- https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tIssue TrackingThird Party Advisory
- https://www.debian.org/security/2018/dsa-4262Third Party Advisory
FAQ
What is CVE-2017-16653?
CVE-2017-16653 is a vulnerability with a CVSS score of 5.9 (MEDIUM). 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...
How severe is CVE-2017-16653?
CVE-2017-16653 has been rated MEDIUM with a CVSS base score of 5.9/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2017-16653?
Check the references section above for vendor advisories and patch information. Affected products include: Sensiolabs Symfony, Debian Debian Linux.