CVE-2017-16653

Name	CVE-2017-16653
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.
Source	CVE (at NVD; CERT, LWN, oss-sec, fulldisc, bugtraq, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, Mageia, GitHub code/issues, web search, more)
References	DSA-4262-1
NVD severity	medium

Vulnerable and fixed packages

The table below lists information on source packages.

Source Package	Release	Version	Status
symfony (PTS)	stretch (security), stretch	2.8.7+dfsg-1.3+deb9u3	fixed
	buster, buster (security)	3.4.22+dfsg-2+deb10u1	fixed
	bullseye	4.4.19+dfsg-2	fixed
	bookworm, sid	5.4.2+dfsg-3	fixed

The information below is based on the following data on fixed versions.

Package	Type	Release	Fixed Version	Origin
symfony	source	jessie	(not affected)
symfony	source	stretch	2.8.7+dfsg-1.3+deb9u1	DSA-4262-1
symfony	source	(unstable)	3.4.0+dfsg-1

Notes

[jessie] - symfony <not-affected> (vulnerable code not present in branch 2.3)
https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https
https://github.com/symfony/symfony/pull/24992