CVE-2024-50341 is a low-severity (CVSS 3.1) Improper Authentication vulnerability in symfony/security-bundle. A fix is available for symfony/security-bundle — see the affected versions and patch details below.
Security::login does not take into account custom user_checker in symfony/security-bundle
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-50341.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
symfony/security-bundle🐘symfony/security-bundle🐘symfony/security-bundle🐘symfony/symfony🐘symfony/symfony🐘symfony/symfonyReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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 user_checker 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 user_checker. All users are advised to upgrade. There are no known workarounds for this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/security-bundle | ≥ 6.2.0&&< 6.4.10 | 6.4.10composer require symfony/security-bundle:^6.4.10 |
| 🐘Packagist | symfony/security-bundle | ≥ 7.0.0&&< 7.0.10 | 7.0.10composer require symfony/security-bundle:^7.0.10 |
| 🐘Packagist | symfony/security-bundle | ≥ 7.1.0&&< 7.1.3 | 7.1.3composer require symfony/security-bundle:^7.1.3 |
| 🐘Packagist | symfony/symfony | ≥ 6.2.0&&< 6.4.10 | 6.4.10composer require symfony/symfony:^6.4.10 |
| 🐘Packagist | symfony/symfony | ≥ 7.0.0&&< 7.0.10 | 7.0.10composer require symfony/symfony:^7.0.10 |
| 🐘Packagist | symfony/symfony | ≥ 7.1.0&&< 7.1.3 | 7.1.3composer require symfony/symfony:^7.1.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/security-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/security-bundle to 6.4.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-50341 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2024-50341 in your dependencies?
Find it across Packagist, including transitive dependencies.