CVE-2024-50341: Symfony Security Bundle User Checker Bypass Vulnerability

symfony/security-bundle Updated 02 Oct 2025

Summary

06/11/2024
Yes i
Low
3.1

CVE-2024-50341: Symfony's Security::login does not take into account custom user_checker. Affects symfony/security-bundle across 3 version ranges.

>= 6.2.0, < 6.4.10 >= 7.0.0, < 7.0.10 >= 7.1.0, < 7.1.3

Fixed in 6.4.10, 7.0.10 or 7.1.3, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2024-50341 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Symfony is a robust PHP framework widely used for building web applications. The Symfony Security Bundle provides essential security features, including authentication and authorization. It allows developers to define custom user checkers to enforce specific security rules during user login. However, a flaw in the Security::login method can lead to unauthorized access, as it does not invoke the custom user checker, potentially compromising application security.

Vulnerability Detail

The vulnerability arises from the Security::login method in Symfony's Security Bundle, which fails to call the configured custom user_checker during programmatic login. This oversight allows users to log in without the necessary checks, leading to unauthorized access. The issue is particularly concerning as it can be exploited by attackers to gain access to sensitive areas of an application without proper validation, undermining the security model established by the developers.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 6.2.0, < 6.4.10 6.4.10
    composer require symfony/security-bundle:6.4.10
  • >= 7.0.0, < 7.0.10 7.0.10
    composer require symfony/security-bundle:7.0.10
  • >= 7.1.0, < 7.1.3 7.1.3
    composer require symfony/security-bundle:7.1.3

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a temporary workaround, developers can implement additional checks in their login logic to ensure that the custom user checker is manually invoked before allowing a user to log in. However, this is not a permanent solution and should be replaced with the official patch as soon as possible.

Conclusion

The CVE-2024-50341 vulnerability in the Symfony Security Bundle poses a significant risk by allowing unauthorized logins. It is crucial for developers to update to the patched versions to safeguard their applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for symfony/security-bundle →

Share this vulnerability

FAQ

CVE-2024-50341 is a vulnerability in the Symfony Security Bundle that allows unauthorized login due to the failure of the Security::login method to call the custom user checker.

You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to analyze your composer.lock file without any signup.

The main consequence is unauthorized access to applications, which can lead to data breaches and compromise sensitive information.

To apply the patch, update your Symfony Security Bundle to one of the fixed versions: 6.4.10, 7.0.10, or 7.1.3 using Composer.

Yes, you can implement additional checks in your login logic to manually invoke the custom user checker, but this should only be a temporary measure.

Related vulnerabilities

Recent vulnerabilities recorded for symfony/security-bundle.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 6.2.0, < 6.4.10 6.4.10
    composer require symfony/security-bundle:6.4.10
  • >= 7.0.0, < 7.0.10 7.0.10
    composer require symfony/security-bundle:7.0.10
  • >= 7.1.0, < 7.1.3 7.1.3
    composer require symfony/security-bundle:7.1.3

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback