CVE-2024-50341: Security::login does not take into account custom user_checker

Published Jul 17, 2024
·
Updated

Description

The custom userchecker defined on a firewall is not called when Login Programmaticaly with the Security::login method, leading to unwanted login.

Resolution

The Security::login method now ensure to call the configured userchecker.

The patch for this issue is available here for branch 6.4.

Credits

We would like to thank Oleg Andreyev, Antoine MAKDESSI for reporting the issue and Christian Flothmann for providing the fix.

Other sources

CVE-2024-50341: Security::login does not take into account custom userchecker

— Packagist

symfony/security-bundle is a module for the Symphony PHP framework which provides a tight integration of the Security component into the Symfony full-stack framework. The custom userchecker defined on a firewall is not called when Login Programmaticaly with the Security::login method, leading to unwanted login. As of versions 6.4.10, 7.0.10 and 7.1.3 the Security::login method now ensure to call the configured userchecker. All users are advised to upgrade. There are no known workarounds for this vulnerability.

— NVD

Affected Software

19 affected componentsFixes available
composer/symfony/symfony>=7.1.0<7.1.3
7.1.3
composer/symfony/symfony>=7.0.0<7.0.10
7.0.10
composer/symfony/symfony>=6.2.0<6.4.10
6.4.10
composer/symfony/security-bundle>=7.1.0<7.1.3
7.1.3
composer/symfony/security-bundle>=7.0.0<7.0.10
7.0.10
composer/symfony/security-bundle>=6.2.0<6.4.10
6.4.10
composer/symfony/symfony>=6.2.0, <6.3.0
composer/symfony/symfony>=6.3.0, <6.4.0
composer/symfony/symfony>=6.4.0, <6.4.10
6.4.10
composer/symfony/symfony>=7.0.0, <7.0.10
7.0.10
composer/symfony/symfony>=7.1.0, <7.1.3
7.1.3
composer/symfony/security-bundle>=6.2.0, <6.3.0
composer/symfony/security-bundle>=6.3.0, <6.4.0
composer/symfony/security-bundle>=6.4.0, <6.4.10
6.4.10
composer/symfony/security-bundle>=7.0.0, <7.0.10
7.0.10
composer/symfony/security-bundle>=7.1.0, <7.1.3
7.1.3
debian/symfony<6.4.10+dfsg-1
6.4.10+dfsg-1
debian/symfony<6.4.10+dfsg-1
6.4.10+dfsg-1
debian/symfony
5.4.53+dfsg-0+deb12u16.4.41+dfsg-0+deb13u17.4.22+dfsg-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 7.1.3
  2. Upgrade

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

    Fixed in 7.0.10
  3. Upgrade

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

    Fixed in 6.4.10
  4. Upgrade

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

    Fixed in 7.1.3
  5. Upgrade

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

    Fixed in 7.0.10
  6. Upgrade

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

    Fixed in 6.4.10
  7. Upgrade

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

    Fixed in 6.4.10+dfsg-1
  8. Upgrade

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

    Fixed in 5.4.53+dfsg-0+deb12u1Fixed in 6.4.41+dfsg-0+deb13u1Fixed in 7.4.22+dfsg-1
  9. Upgrade

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

    Fixed in 6.4.10
  10. Upgrade

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

    Fixed in 7.0.10
  11. Upgrade

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

    Fixed in 7.1.3

Event History

Jul 17, 2024
Advisory Published
via Packagist·08:00 AM
Data Sourced
via Packagist·08:00 AM
DescriptionSeverityAffected Software
Nov 6, 2024
Advisory Published
via GitHub·03:13 PM
CVE Published
via MITRE·09:06 PM
Data Sourced
via MITRE·09:06 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·09:15 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-50341?

CVE-2024-50341 has a critical severity due to the potential for unauthorized logins.

2

How do I fix CVE-2024-50341?

To fix CVE-2024-50341, update the Symfony package to version 7.1.3, 7.0.10, or 6.4.10.

3

What versions of Symfony are affected by CVE-2024-50341?

CVE-2024-50341 affects Symfony versions between 6.2.0 and 6.4.10, 7.0.0 and 7.0.10, and 7.1.0 and 7.1.3.

4

What is the impact of not resolving CVE-2024-50341?

Not resolving CVE-2024-50341 may allow attackers to gain unauthorized access to user accounts.

5

Is CVE-2024-50341 related to the Security::login method in Symfony?

Yes, CVE-2024-50341 specifically involves the Security::login method not calling the configured user_checker.

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