First published: Thu Nov 16 2017(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
composer/symfony/symfony | >=2.7.0<2.7.38>=2.8.0<2.8.31>=3.0.0<3.1.0>=3.1.0<3.2.0>=3.2.0<3.2.14>=3.3.0<3.3.13 | |
composer/symfony/security-csrf | >=2.7.0<2.7.38>=2.8.0<2.8.31>=3.0.0<3.1.0>=3.1.0<3.2.0>=3.2.0<3.2.14>=3.3.0<3.3.13 | |
composer/symfony/security | >=2.7.0<2.7.38>=2.8.0<2.8.31>=3.0.0<3.1.0>=3.1.0<3.2.0>=3.2.0<3.2.14>=3.3.0<3.3.13 | |
SensioLabs Symfony | >=2.7.0<=2.7.37 | |
SensioLabs Symfony | >=3.2.0<=3.2.13 | |
SensioLabs Symfony | >=3.3.0<=3.3.12 | |
SensioLabs Symfony | >=3.8.0<=3.8.30 | |
Debian Debian Linux | =9.0 | |
debian/symfony | 3.4.22+dfsg-2+deb10u1 3.4.22+dfsg-2+deb10u2 4.4.19+dfsg-2+deb11u3 5.4.23+dfsg-1 5.4.29+dfsg-1 5.4.30+dfsg-1 | |
composer/symfony/symfony | >=3.3.0<3.3.13 | 3.3.13 |
composer/symfony/symfony | >=3.0.0<3.2.14 | 3.2.14 |
composer/symfony/symfony | >=2.8.0<2.8.31 | 2.8.31 |
composer/symfony/symfony | >=2.7.0<2.7.38 | 2.7.38 |
composer/symfony/security | >=3.3.0<3.3.13 | 3.3.13 |
composer/symfony/security | >=3.0.0<3.2.14 | 3.2.14 |
composer/symfony/security | >=2.8.0<2.8.31 | 2.8.31 |
composer/symfony/security | >=2.7.0<2.7.38 | 2.7.38 |
composer/symfony/security-csrf | >=3.3.0<3.3.13 | 3.3.13 |
composer/symfony/security-csrf | >=3.0.0<3.2.14 | 3.2.14 |
composer/symfony/security-csrf | >=2.8.0<2.8.31 | 2.8.31 |
composer/symfony/security-csrf | >=2.7.0<2.7.38 | 2.7.38 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The CVE ID for this vulnerability is CVE-2017-16653.
The severity level of CVE-2017-16653 is medium, with a severity value of 5.9.
Versions before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5 of Symfony are affected by CVE-2017-16653.
This vulnerability can be exploited through a MITM (Man-in-the-Middle) attack on HTTP to obtain the CSRF token and use it in HTTPS.
You can find more information about CVE-2017-16653 on the Symfony website, the NIST NVD website, and the GitHub pull request.