CVE-2022-24895: Symfony vulnerable to Session Fixation of CSRF tokens

CVE-2022-24895 · Severity: low · CVSS 3.1 · Published 2023-02-01

Symfony vulnerable to Session Fixation of CSRF tokens

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

Quick answers

Is CVE-2022-24895 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-24895 being exploited in the wild.
How severe is CVE-2022-24895?
Low severity, with a CVSS score of 3.1, published 1 February 2023.
Which products and versions are affected?
symfony/security-bundle (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=4.4.50; symfony/symfony (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=4.4.50.
Is there a fix for CVE-2022-24895?
Yes. symfony/security-bundle (Packagist): upgrade to 4.4.50 or later; symfony/symfony (Packagist): upgrade to 4.4.50 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-24895?
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 4.4.50 or later
    composer require symfony/security-bundle:^4.4.50
  • symfony/symfony (Packagist): upgrade to 4.4.50 or later
    composer require symfony/symfony:^4.4.50

Affected products

  • symfony/security-bundle (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=4.4.50
  • symfony/symfony (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=4.4.50

Identifiers

  • CVE-2022-24895
  • GHSA-3gv2-29qc-v67m

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