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
| Link | Resource |
|---|---|
| https://github.com/symfony/symfony/pull/24992 | Issue Tracking Third Party Advisory |
| https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https | Issue Tracking Third Party Advisory |
| https://www.debian.org/security/2018/dsa-4262 | Third Party Advisory |
| https://github.com/symfony/symfony/pull/24992 | Issue Tracking Third Party Advisory |
| https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https | Issue Tracking Third Party Advisory |
| https://www.debian.org/security/2018/dsa-4262 | Third Party Advisory |
Configurations
History
21 Nov 2024, 03:16
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/symfony/symfony/pull/24992 - Issue Tracking, Third Party Advisory | |
| References | () https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https - Issue Tracking, Third Party Advisory | |
| References | () https://www.debian.org/security/2018/dsa-4262 - Third Party Advisory |
Information
Published : 2018-08-06 21:29
Updated : 2024-11-21 03:16
NVD link : CVE-2017-16653
Mitre link : CVE-2017-16653
CVE.ORG link : CVE-2017-16653
JSON object : View
Products Affected
debian
- debian_linux
sensiolabs
- symfony
CWE