CVE-2018-11408: Open redirect vulnerability on security handlers

Published May 25, 2018
·
Updated

CVE-2018-11408: Open redirect vulnerability on security handlers

Other sources

The security handlers in the Security component in Symfony in 2.7.x before 2.7.48, 2.8.x before 2.8.41, 3.3.x before 3.3.17, 3.4.x before 3.4.11, and 4.0.x before 4.0.11 have an Open redirect vulnerability when security.httputils is inlined by a container. NOTE: this issue exists because of an incomplete fix for CVE-2017-16652.

Affected Software

34 affected componentsFixes available
composer/symfony/symfony>=2.7.38, <2.7.48, >=2.8.0, <2.8.41, >=3.0.0, <3.1.0, >=3.1.0, <3.2.0, >=3.2.0, <3.3.0, >=3.3.0, <3.3.17, >=3.4.0, <3.4.11, >=4.0.0, <4.0.11
composer/symfony/security-bundle>=2.7.38, <2.7.48, >=2.8.0, <2.8.41, >=3.0.0, <3.1.0, >=3.1.0, <3.2.0, >=3.2.0, <3.3.0, >=3.3.0, <3.3.17, >=3.4.0, <3.4.11, >=4.0.0, <4.0.11
composer/symfony/security-bundle>=4.0.0<4.0.11
4.0.11
composer/symfony/security-bundle>=3.4.0<3.4.11
3.4.11
composer/symfony/security-bundle>=3.3.0<3.3.17
3.3.17
composer/symfony/security-bundle>=2.8.0<2.8.41
2.8.41
composer/symfony/security-bundle>=2.7.0<2.7.48
2.7.48
composer/symfony/symfony>=4.0.0<4.0.11
4.0.11
composer/symfony/symfony>=3.4.0<3.4.11
3.4.11
composer/symfony/symfony>=3.3.0<3.3.17
3.3.17
composer/symfony/symfony>=2.8.0<2.8.41
2.8.41
composer/symfony/symfony>=2.7.0<2.7.48
2.7.48
SensioLabs Symfony>=2.7.0<2.7.48
SensioLabs Symfony>=2.8.0<2.8.41
SensioLabs Symfony>=3.3.0<3.3.17
SensioLabs Symfony>=3.4.0<3.4.11
SensioLabs Symfony>=4.0.0<4.0.11
Debian Debian Linux=8.0
composer/symfony/symfony>=2.7.38, <2.7.48
2.7.48
composer/symfony/symfony>=2.8.0, <2.8.41
2.8.41
composer/symfony/symfony>=3.0.0, <3.1.0
composer/symfony/symfony>=3.1.0, <3.2.0
composer/symfony/symfony>=3.2.0, <3.3.0
composer/symfony/symfony>=3.3.0, <3.3.17
3.3.17
composer/symfony/symfony>=3.4.0, <3.4.11
3.4.11
composer/symfony/symfony>=4.0.0, <4.0.11
4.0.11
composer/symfony/security-bundle>=2.7.38, <2.7.48
2.7.48
composer/symfony/security-bundle>=2.8.0, <2.8.41
2.8.41
composer/symfony/security-bundle>=3.0.0, <3.1.0
composer/symfony/security-bundle>=3.1.0, <3.2.0
composer/symfony/security-bundle>=3.2.0, <3.3.0
composer/symfony/security-bundle>=3.3.0, <3.3.17
3.3.17
composer/symfony/security-bundle>=3.4.0, <3.4.11
3.4.11
composer/symfony/security-bundle>=4.0.0, <4.0.11
4.0.11

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/symfony/security-bundle to a version that resolves this vulnerability.

    Fixed in 4.0.11
  2. Upgrade

    Upgrade composer/symfony/security-bundle to a version that resolves this vulnerability.

    Fixed in 3.4.11
  3. Upgrade

    Upgrade composer/symfony/security-bundle to a version that resolves this vulnerability.

    Fixed in 3.3.17
  4. Upgrade

    Upgrade composer/symfony/security-bundle to a version that resolves this vulnerability.

    Fixed in 2.8.41
  5. Upgrade

    Upgrade composer/symfony/security-bundle to a version that resolves this vulnerability.

    Fixed in 2.7.48
  6. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 4.0.11
  7. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 3.4.11
  8. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 3.3.17
  9. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.8.41
  10. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.7.48
  11. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 2.7.48
  12. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 2.8.41
  13. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 3.3.17
  14. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 3.4.11
  15. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 4.0.11

Event History

May 25, 2018
Advisory Published
via Packagist·11:46 AM
Data Sourced
via Packagist·11:46 AM
DescriptionSeverityAffected Software
Advisory Published
02:04 PM
Jun 13, 2018
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description

Frequently Asked Questions

1

What is CVE-2018-11408?

CVE-2018-11408 is an open redirect vulnerability in the security handlers of Symfony.

2

What is the severity of CVE-2018-11408?

The severity of CVE-2018-11408 is medium (6.1).

3

Which versions of Symfony are affected by CVE-2018-11408?

Symfony versions 2.7.x before 2.7.48, 2.8.x before 2.8.41, 3.3.x before 3.3.17, 3.4.x before 3.4.11, and 4.0.x before 4.0.11 are affected by CVE-2018-11408.

4

How can I fix CVE-2018-11408?

To fix CVE-2018-11408, you should update Symfony to version 2.7.48, 2.8.41, 3.3.17, 3.4.11, or 4.0.11.

5

Where can I find more information about CVE-2018-11408?

You can find more information about CVE-2018-11408 at the following references: 1. [Symfony Security Advisory](https://symfony.com/cve-2018-11408) 2. [National Vulnerability Database (NVD)](https://nvd.nist.gov/vuln/detail/CVE-2018-11408) 3. [Debian LTS Announcement](https://lists.debian.org/debian-lts-announce/2019/03/msg00009.html)

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203