VYPR
Moderate severityNVD Advisory· Published Jun 13, 2018· Updated Aug 5, 2024

CVE-2017-16652

CVE-2017-16652

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Symfony's authentication handlers create an open redirect via the _target_path parameter, enabling phishing attacks.

Vulnerability

In Symfony versions 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, the DefaultAuthenticationSuccessHandler and DefaultAuthenticationFailureHandler classes use the _target_path request parameter to build a redirect response after authentication. No validation is performed to ensure the path is relative or belongs to the same domain, so an attacker can supply an absolute URL pointing to an external domain. This flaw is an open redirect vulnerability [1][2].

Exploitation

An attacker needs to craft a login URL that includes a _target_path parameter whose value is an absolute URL to an external site under their control (e.g., https://evil.com/). When a user clicks such a link and completes the Symfony authentication process, the success or failure handler will redirect the user to that external URL. The attacker does not require any special network position or authentication; user interaction (clicking the crafted link and logging in) is sufficient [1][3].

Impact

Successful exploitation allows an attacker to redirect users from a legitimate Symfony application to an arbitrary external domain. This open redirect can be leveraged for phishing campaigns, tricking users into entering credentials or sensitive information on a malicious site that appears to be the legitimate application, thereby compromising confidentiality and trust [1].

Mitigation

Symfony addressed this issue in versions 2.7.38, 2.8.31, 3.2.14, and 3.3.13. Users running affected versions should upgrade immediately to the corresponding patched release. No workaround is described in the available references [4].

AI Insight generated on May 22, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
symfony/symfonyPackagist
>= 2.7.0, < 2.7.382.7.38
symfony/symfonyPackagist
>= 2.8.0, < 2.8.312.8.31
symfony/symfonyPackagist
>= 3.2.0, < 3.2.143.2.14
symfony/symfonyPackagist
>= 3.3.0, < 3.3.133.3.13
symfony/security-httpPackagist
>= 2.7.0, < 2.7.382.7.38
symfony/security-httpPackagist
>= 2.8.0, < 2.8.312.8.31
symfony/security-httpPackagist
>= 3.2.0, < 3.2.143.2.14
symfony/security-httpPackagist
>= 3.3.0, < 3.3.133.3.13
symfony/securityPackagist
>= 2.7.0, < 2.7.382.7.38
symfony/securityPackagist
>= 2.8.0, < 2.8.312.8.31
symfony/securityPackagist
>= 3.2.0, < 3.2.143.2.14
symfony/securityPackagist
>= 3.3.0, < 3.3.133.3.13

Affected products

3

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

8

News mentions

0

No linked articles in our index yet.