CVEvulnerability
CVE-2017-16653
5.9 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2018-08-06
- Last modified
- 2026-06-17
- Assigner
- [email protected]
- CVSS 3.0 ([email protected])
- 5.9 MEDIUM — CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- CVSS 2.0 ([email protected])
- 4.3 MEDIUM — AV:N/AC:M/Au:N/C:P/I:N/A:N
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.
Affected configurations
• 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
References
- 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