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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-4262-1 | symfony security update |
EUVD |
EUVD-2022-3279 | 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. |
Github GHSA |
GHSA-92x6-h2gr-8gxq | Symfony CSRF Vulnerability |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-05T20:27:04.403Z
Reserved: 2017-11-07T00:00:00
Link: CVE-2017-16653
No data.
Status : Modified
Published: 2018-08-06T21:29:00.283
Modified: 2024-11-21T03:16:46.210
Link: CVE-2017-16653
No data.
OpenCVE Enrichment
No data.
Debian DSA
EUVD
Github GHSA