Symfony 2.7.0 to 2.7.37, 2.8.0 to 2.8.30, 3.2.0 to 3.2.13, and 3.3.0 to 3.3.12 versions of the Symfony Security component are affected by this security issue.
The issue has been fixed in Symfony 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5.
Note that no fixes are provided for Symfony 3.0 and 3.1 as they are not maintained anymore.
DefaultAuthenticationSuccessHandler
or DefaultAuthenticationFailureHandler
take
the content of the _target_path
parameter and generate a redirect response but no
check is performed on the path, which could be an absolute URL to an external domain,
opening redirect vulnerability.
Open redirect vulnerability are not too much considered but they can be exploited for example to mount effective phishing attacks.
The fix forces the redirect target to be within the scope of the session cookie.
The allowed redirect targets must now match the cookie_domain
and cookie_secure
configuration options.
The patch for this issue is available here.
I would like to thank Stefano Angaran for reporting this security issue, Nicolas Grekas for providing a fix, and the Symfony Core Team for reviewing the patch.
What a Symfony developer should know about the framework: News, Jobs, Tweets, Events, Videos,...