{"id":"CVE-2017-16653","published":"2018-08-06T21:00:00Z","modified":"2024-08-05T20:27:04Z","title":"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","vendor":null,"product":null,"tier":"tail","description":{"text":"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.","provenance":"source","from":"CVE.org"},"cvss":null,"epss":{"score":0.01486,"percentile":0.7466,"provenance":"source"},"cwes":[],"references":[{"url":"https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https","tags":["x_refsource_CONFIRM"]},{"url":"https://github.com/symfony/symfony/pull/24992","tags":["x_refsource_CONFIRM"]},{"url":"https://www.debian.org/security/2018/dsa-4262","tags":["vendor-advisory","x_refsource_DEBIAN"]}],"priority":{"score":14.9,"factors":[{"name":"EPSS percentile","points":14.93}]},"affected":[{"ecosystem":"Packagist","package":"symfony/security-csrf","vulnerableRanges":[">=2.7.0, <2.7.38",">=2.8.0, <2.8.31",">=3.0.0, <3.2.14",">=3.3.0, <3.3.13"],"patched":["2.7.38","2.8.31","3.2.14","3.3.13"],"from":["GHSA-92x6-h2gr-8gxq"],"provenance":"source"},{"ecosystem":"Packagist","package":"symfony/security","vulnerableRanges":[">=2.7.0, <2.7.38",">=2.8.0, <2.8.31",">=3.0.0, <3.2.14",">=3.3.0, <3.3.13"],"patched":["2.7.38","2.8.31","3.2.14","3.3.13"],"from":["GHSA-92x6-h2gr-8gxq"],"provenance":"source"},{"ecosystem":"Packagist","package":"symfony/symfony","vulnerableRanges":[">=2.7.0, <2.7.38",">=2.8.0, <2.8.31",">=3.0.0, <3.2.14",">=3.3.0, <3.3.13"],"patched":["2.7.38","2.8.31","3.2.14","3.3.13"],"from":["GHSA-92x6-h2gr-8gxq"],"provenance":"source"}],"summary":{"text":"The flaw lies in the CSRF protection implementation of Symfony, affecting versions before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5, because it uses the same token for HTTP and HTTPS. An attacker in a position to intercept HTTP traffic (a man-in-the-middle) can capture the token and replay it in an HTTPS context to carry out cross-site request forgery attacks.","provenance":"ai","model":"claude-haiku-5-5","generatedAt":"2026-11-20T21:45:17Z"},"euvd":{"id":"EUVD-2022-3279","exploited":false,"provenance":"source"}}