CVE-2024-50341: Symfony's `Security::login` does not take into account custom `user_checker`

CVE-2024-50341 · Severity: low · CVSS 3.1 · Published 2024-11-06

Symfony's `Security::login` does not take into account custom `user_checker`

Technologies: symfony/security-bundle (Packagist), symfony/symfony (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2024-50341 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-50341 being exploited in the wild.
How severe is CVE-2024-50341?
Low severity, with a CVSS score of 3.1, published 6 November 2024.
Which products and versions are affected?
symfony/security-bundle (Packagist) ECOSYSTEM:introduced=6.2.0,fixed=6.4.10; symfony/symfony (Packagist) ECOSYSTEM:introduced=6.2.0,fixed=6.4.10.
Is there a fix for CVE-2024-50341?
Yes. symfony/security-bundle (Packagist): upgrade to 6.4.10 or later; symfony/symfony (Packagist): upgrade to 6.4.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-50341?
Check whether you run symfony/security-bundle (Packagist) or symfony/symfony (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • symfony/security-bundle (Packagist): upgrade to 6.4.10 or later
    composer require symfony/security-bundle:^6.4.10
  • symfony/symfony (Packagist): upgrade to 6.4.10 or later
    composer require symfony/symfony:^6.4.10

Affected products

  • symfony/security-bundle (Packagist) ECOSYSTEM:introduced=6.2.0,fixed=6.4.10
  • symfony/symfony (Packagist) ECOSYSTEM:introduced=6.2.0,fixed=6.4.10

Identifiers

  • CVE-2024-50341
  • GHSA-jxgr-3v7q-3w9v

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.