CVE-2022-24895 json
Symfony vulnerable to Session Fixation of CSRF tokens
published 2023-02-01 3 y ago modified 2026-06-17 4 mo ago also BIT-symfony-2022-24895 , EUVD-2023-0611 , GHSA-3gv2-29qc-v67m
- cvss
- 6.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. When authenticating users Symfony by default regenerates the session ID upon login, but preserves the rest of session attributes. Because this does not clear CSRF tokens upon login, this might enables same-site attackers to bypass the CSRF protection mechanism by performing an attack similar to a session-fixation. This issue has been fixed in the 4.4 branch.
Patch / fix
- packagist symfony/security-bundle 4.4.50, 5.4.20, 6.0.20, 6.1.12, 6.2.6
- packagist symfony/symfony 4.4.50, 5.4.20, 6.0.20, 6.1.12, 6.2.6
- bitnami symfony 4.4.50, 5.4.20, 6.0.20, 6.1.12, 6.2.6
- sensiolabs symfony 4.4.50, 5.4.20, 6.0.20, 6.1.12, 6.2.6
- symfony Debian 14, Debian 13, Debian 12 5.4.20+dfsg-1
debian advisories DEBIAN-CVE-2022-24895
- symfony Ubuntu Pro 20.04 LTS 4.3.8+dfsg-1ubuntu1+esm2
- symfony Ubuntu Pro 22.04 LTS 5.4.4+dfsg-1ubuntu8+esm1
ubuntu advisories UBUNTU-CVE-2022-24895
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-24895 updated
php-symfony: Possible CSRF token fixation
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L |
| GitHub | 3.1 | 6.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | symfony/security-bundle | >=2.0.0, <4.4.50 >=5.0.0, <5.4.20 >=6.0.0, <6.0.20 >=6.1.0, <6.1.12 >=6.2.0, <6.2.6 |
4.4.50 5.4.20 6.0.20 6.1.12 6.2.6 |
| packagist | symfony/symfony | >=2.0.0, <4.4.50 >=5.0.0, <5.4.20 >=6.0.0, <6.0.20 >=6.1.0, <6.1.12 >=6.2.0, <6.2.6 |
4.4.50 5.4.20 6.0.20 6.1.12 6.2.6 |
| bitnami | symfony | >=2.0.0, <4.4.50 >=5.0.0, <5.4.20 >=6.0.0, <6.0.20 >=6.1.0, <6.1.12 >=6.2.0, <6.2.6 |
4.4.50 5.4.20 6.0.20 6.1.12 6.2.6 |
Affected products
- symfony symfony
Classification
References
-
github.com
/symfony/security-bundle/commit/076fd2088ada33d760758d98ff07ddedbf567946
web, patch
-
github.com
/symfony/symfony/commit/5909d74ecee359ea4982fcf4331aaf2e489a1fd4
web, patch
-
github.com
/symfony/symfony/security/advisories/GHSA-3gv2-29qc-v67m
web, patch, third-party-advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/symfony/security-bundle/CVE-2022-24895.yaml
web, issue-tracking
-
lists.debian.org
/debian-lts-announce/2023/07/msg00014.html
web
-
nvd.nist.gov
/vuln/detail/CVE-2022-24895
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2022-24895.yaml
web
-
github.com
/symfony/symfony
package
-
symfony.com
/cve-2022-24895
web
Sources
- CVE List CVE-2022-24895
- GitHub Advisory GHSA-3gv2-29qc-v67m
- NVD CVE-2022-24895
- OSV BIT-symfony-2022-24895
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.