CVE-2018-11385: Session Fixation Issue for Guard Authentication

Published May 25, 2018
·
Updated

An issue was discovered in the Security component in Symfony 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. A session fixation vulnerability within the "Guard" login feature may allow an attacker to impersonate a victim towards the web application if the session id value was previously known to the attacker.

Other sources

CVE-2018-11385: Session Fixation Issue for Guard Authentication

Affected Software

76 affected componentsFixes available
composer/symfony/security>=2.0.0, <2.1.0, >=2.1.0, <2.2.0, >=2.2.0, <2.3.0, >=2.3.0, <2.4.0, >=2.4.0, <2.5.0, >=2.5.0, <2.6.0, >=2.6.0, <2.7.0, >=2.7.0, <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/symfony>=2.0.0, <2.1.0, >=2.1.0, <2.2.0, >=2.2.0, <2.3.0, >=2.3.0, <2.4.0, >=2.4.0, <2.5.0, >=2.5.0, <2.6.0, >=2.6.0, <2.7.0, >=2.7.0, <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-http>=2.4.0, <2.7.48, >=2.5.0, <2.7.48, >=2.6.0, <2.7.48, >=2.7.0, <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-guard>=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
debian/symfony
3.4.22+dfsg-2+deb10u13.4.22+dfsg-2+deb10u24.4.19+dfsg-2+deb11u35.4.23+dfsg-15.4.29+dfsg-15.4.30+dfsg-1
composer/symfony/security>=4.0.0<4.0.11
4.0.11
composer/symfony/security>=3.4.0<3.4.11
3.4.11
composer/symfony/security>=3.0.0<3.3.17
3.3.17
composer/symfony/security>=2.8.0<2.8.41
2.8.41
composer/symfony/security>=2.7.0<2.7.48
2.7.48
composer/symfony/security-http>=4.0.0<4.0.11
4.0.11
composer/symfony/security-http>=3.4.0<3.4.11
3.4.11
composer/symfony/security-http>=3.0.0<3.3.17
3.3.17
composer/symfony/security-http>=2.8.0<2.8.41
2.8.41
composer/symfony/security-http>=2.7.0<2.7.48
2.7.48
composer/symfony/symfony>=3.0.0<3.3.17
3.3.17
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>=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
Debian Debian Linux=9.0
Fedoraproject Fedora=28
composer/symfony/symfony>=2.0.0, <2.1.0
composer/symfony/symfony>=2.1.0, <2.2.0
composer/symfony/symfony>=2.2.0, <2.3.0
composer/symfony/symfony>=2.3.0, <2.4.0
composer/symfony/symfony>=2.4.0, <2.5.0
composer/symfony/symfony>=2.5.0, <2.6.0
composer/symfony/symfony>=2.6.0, <2.7.0
composer/symfony/symfony>=2.7.0, <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-http>=2.4.0, <2.7.48
2.7.48
composer/symfony/security-http>=2.5.0, <2.7.48
2.7.48
composer/symfony/security-http>=2.6.0, <2.7.48
2.7.48
composer/symfony/security-http>=2.7.0, <2.7.48
2.7.48
composer/symfony/security-http>=2.8.0, <2.8.41
2.8.41
composer/symfony/security-http>=3.0.0, <3.1.0
composer/symfony/security-http>=3.1.0, <3.2.0
composer/symfony/security-http>=3.2.0, <3.3.0
composer/symfony/security-http>=3.3.0, <3.3.17
3.3.17
composer/symfony/security-http>=3.4.0, <3.4.11
3.4.11
composer/symfony/security-http>=4.0.0, <4.0.11
4.0.11
composer/symfony/security-guard>=2.8.0, <2.8.41
2.8.41
composer/symfony/security-guard>=3.0.0, <3.1.0
composer/symfony/security-guard>=3.1.0, <3.2.0
composer/symfony/security-guard>=3.2.0, <3.3.0
composer/symfony/security-guard>=3.3.0, <3.3.17
3.3.17
composer/symfony/security-guard>=3.4.0, <3.4.11
3.4.11
composer/symfony/security-guard>=4.0.0, <4.0.11
4.0.11
composer/symfony/security>=2.0.0, <2.1.0
composer/symfony/security>=2.1.0, <2.2.0
composer/symfony/security>=2.2.0, <2.3.0
composer/symfony/security>=2.3.0, <2.4.0
composer/symfony/security>=2.4.0, <2.5.0
composer/symfony/security>=2.5.0, <2.6.0
composer/symfony/security>=2.6.0, <2.7.0
composer/symfony/security>=2.7.0, <2.7.48
2.7.48
composer/symfony/security>=2.8.0, <2.8.41
2.8.41
composer/symfony/security>=3.0.0, <3.1.0
composer/symfony/security>=3.1.0, <3.2.0
composer/symfony/security>=3.2.0, <3.3.0
composer/symfony/security>=3.3.0, <3.3.17
3.3.17
composer/symfony/security>=3.4.0, <3.4.11
3.4.11
composer/symfony/security>=4.0.0, <4.0.11
4.0.11

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 3.4.22+dfsg-2+deb10u1Fixed in 3.4.22+dfsg-2+deb10u2Fixed in 4.4.19+dfsg-2+deb11u3Fixed in 5.4.23+dfsg-1Fixed in 5.4.29+dfsg-1Fixed in 5.4.30+dfsg-1
  2. Upgrade

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

    Fixed in 4.0.11
  3. Upgrade

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

    Fixed in 3.4.11
  4. Upgrade

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

    Fixed in 3.3.17
  5. Upgrade

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

    Fixed in 2.8.41
  6. Upgrade

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

    Fixed in 2.7.48
  7. Upgrade

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

    Fixed in 4.0.11
  8. Upgrade

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

    Fixed in 3.4.11
  9. Upgrade

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

    Fixed in 3.3.17
  10. Upgrade

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

    Fixed in 2.8.41
  11. Upgrade

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

    Fixed in 2.7.48
  12. Upgrade

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

    Fixed in 3.3.17
  13. Upgrade

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

    Fixed in 4.0.11
  14. Upgrade

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

    Fixed in 3.4.11
  15. Upgrade

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

    Fixed in 2.8.41
  16. Upgrade

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

    Fixed in 2.7.48
  17. Upgrade

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

    Fixed in 2.8.41
  18. Upgrade

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

    Fixed in 3.3.17
  19. Upgrade

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

    Fixed in 3.4.11
  20. Upgrade

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

    Fixed in 4.0.11
  21. Upgrade

    Upgrade Symfony Security component to a version that resolves this vulnerability.

    Fixed in 2.7.48
  22. Upgrade

    Upgrade Symfony Security component to a version that resolves this vulnerability.

    Fixed in 2.8.41
  23. Upgrade

    Upgrade Symfony Security component to a version that resolves this vulnerability.

    Fixed in 3.3.17
  24. Upgrade

    Upgrade Symfony Security component to a version that resolves this vulnerability.

    Fixed in 3.4.11
  25. Upgrade

    Upgrade Symfony Security component 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-11385?

CVE-2018-11385 is a session fixation issue in the Security component in Symfony which allows an attacker to impersonate a victim.

2

What is the severity of CVE-2018-11385?

CVE-2018-11385 has a severity value of 8.1 (High).

3

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

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-11385.

4

How can I fix the session fixation issue in Symfony?

To fix the session fixation issue in Symfony, you should upgrade to the latest patched version of Symfony in the affected minor versions (2.7.x, 2.8.x, 3.3.x, 3.4.x, or 4.0.x).

5

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

You can find more information about CVE-2018-11385 on the Symfony website (https://symfony.com/cve-2018-11385) and the NIST NVD (https://nvd.nist.gov/vuln/detail/CVE-2018-11385).

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