CVE-2017-16653
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.
Does this matter?
Lower severity and a low EPSS score (1.47%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.0
- 5.9 MEDIUMCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- 1.47% probability · 72th percentile
- CISA KEV
- Not listed
- Affected
- sensiolabs/symfony · debian/debian linux
- Source
- cve@mitre.org
References
- https://github.com/symfony/symfony/pull/24992Issue Tracking, Third Party Advisory
- https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-httpsIssue Tracking, Third Party Advisory
- https://www.debian.org/security/2018/dsa-4262Third Party Advisory
- https://github.com/symfony/symfony/pull/24992Issue Tracking, Third Party Advisory
- https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-httpsIssue Tracking, Third Party Advisory
- https://www.debian.org/security/2018/dsa-4262Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.