CVE-2017-16653
- Source
- https://cve.org/CVERecord?id=CVE-2017-16653
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2017-16653.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2017-16653
- Aliases
- Downstream
- Published
- 2018-08-06T21:29:00.283Z
- Modified
- 2026-02-24T11:20:58.761475Z
- Severity
-
- 5.9 (Medium) CVSS_V3 - CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N CVSS Calculator
- Summary
- [none]
- Details
-
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://github.com/symfony/symfony/pull/24992
- https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https
- https://www.debian.org/security/2018/dsa-4262
- https://github.com/symfony/symfony/pull/24992
- https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https