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.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.7.38, 2.8.31, 3.2.14, 3.3.13
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- symfony/symfonyPackagist
From 2.7.0 · fixed in 2.7.38
- symfony/symfonyPackagist
From 2.8.0 · fixed in 2.8.31
- symfony/symfonyPackagist
From 3.2.0 · fixed in 3.2.14
- symfony/symfonyPackagist
From 3.3.0 · fixed in 3.3.13
- symfony/security-httpPackagist
From 2.7.0 · fixed in 2.7.38
- symfony/security-httpPackagist
From 2.8.0 · fixed in 2.8.31
- symfony/security-httpPackagist
From 3.2.0 · fixed in 3.2.14
- symfony/security-httpPackagist
From 3.3.0 · fixed in 3.3.13
- symfony/securityPackagist
From 2.7.0 · fixed in 2.7.38
- symfony/securityPackagist
From 2.8.0 · fixed in 2.8.31
- symfony/securityPackagist
From 3.2.0 · fixed in 3.2.14
- symfony/securityPackagist
From 3.3.0 · fixed in 3.3.13