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.
References:
https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https
Created php-symfony tracking bugs for this issue:
Affects: epel-7 [bug 1620268]
Affects: fedora-27 [bug 1620267]
Created php-symfony3 tracking bugs for this issue:
Affects: fedora-28 [bug 1620270]
Created php-symfony4 tracking bugs for this issue:
Affects: fedora-all [bug 1620269]
Comment 2Product Security DevOps Team
2019-06-10 10:36:25 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.