CVE-2017-16653
low-risk
Published 2018-08-06
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.
Do I need to act?
-
0.33% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.9/10
Medium
NETWORK
/ HIGH complexity
Affected Products (2)
Affected Vendors
References (6)
Issue Tracking
https://github.com/symfony/symfony/pull/24992
Third Party Advisory
https://www.debian.org/security/2018/dsa-4262
Issue Tracking
https://github.com/symfony/symfony/pull/24992
Third Party Advisory
https://www.debian.org/security/2018/dsa-4262
26
/ 100
low-risk
Severity
18/34 · Moderate
Exploitability
1/34 · Minimal
Exposure
7/34 · Low