Symfony Open Redirect
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/symfony Packagist |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| symfony/symfony Packagist |
|
|
| symfony/security-http Packagist |
|
|
| symfony/security Packagist |
|
|
An issue was discovered in Symfony 2.7.x before 2.7.38, 2.8.x before 2.8.31, 3.2.x before 3.2.14, and 3.3.x before 3.3.13. DefaultAuthenticationSuccessHandler or DefaultAuthenticationFailureHandler takes the content of the _target_path parameter and generates a redirect response, but no check is performed on the path, which could be an absolute URL to an external domain. This Open redirect vulnerability can be exploited for example to mount effective phishing attacks.
From the CVE record · mitre
Symfony’s DefaultAuthenticationSuccessHandler and DefaultAuthenticationFailureHandler do not validate the _target_path parameter before generating a redirect. An attacker can use an external URL in that parameter to redirect a user to another domain, potentially for phishing. The input does not specify whether authentication is required.
Teams using Packagist symfony/symfony, symfony/security-http, or symfony/security in versions 2.7.0–2.7.37, 2.8.0–2.8.30, 3.2.0–3.2.13, or 3.3.0–3.3.12 should check their installations.