# CVE-2022-24895: Symfony vulnerable to Session Fixation of CSRF tokens > Attackers can bypass CSRF protection in Symfony by exploiting session fixation during login, allowing unauthorized actions on behalf of authenticated users. - **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 3 Feb 2023 - **Updated:** 10 Mar 2025 - **Also known as:** BIT-symfony-2022-24895, DEBIAN-CVE-2022-24895, GHSA-3gv2-29qc-v67m, UBUNTU-CVE-2022-24895 ## What is CVE-2022-24895? CVE-2022-24895 is a medium-severity vulnerability in Sensiolabs Symfony, published on 3 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration), CWE-384 (Session Fixation) ## Which versions are affected by CVE-2022-24895? 21 open source packages ship an affected version, including symfony/security-bundle, symfony and symfony/symfony. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `symfony/security-bundle` | Packagist | From 2.0.0 | 4.4.50 | | `symfony/security-bundle` | Packagist | From 2.0.0 | 4.4.50 | | `symfony/security-bundle` | Packagist | From 5.0.0 | 5.4.20 | | `symfony/security-bundle` | Packagist | From 5.0.0 | 5.4.20 | | `symfony/security-bundle` | Packagist | From 6.0.0 | 6.0.20 | | `symfony/security-bundle` | Packagist | From 6.0.0 | 6.0.20 | | `symfony/security-bundle` | Packagist | From 6.1.0 | 6.1.12 | | `symfony/security-bundle` | Packagist | From 6.1.0 | 6.1.12 | | `symfony/security-bundle` | Packagist | From 6.2.0 | 6.2.6 | | `symfony/security-bundle` | Packagist | From 6.2.0 | 6.2.6 | | `symfony` | Bitnami | From 2.0.0 | 4.4.50, 5.4.20, 6.0.20, 6.1.12, 6.2.6 | | `symfony/symfony` | Packagist | From 2.0.0 | 4.4.50 | | `symfony/symfony` | Packagist | From 2.0.0 | 4.4.50 | | `symfony/symfony` | Packagist | From 5.0.0 | 5.4.20 | | `symfony/symfony` | Packagist | From 5.0.0 | 5.4.20 | | `symfony/symfony` | Packagist | From 6.0.0 | 6.0.20 | | `symfony/symfony` | Packagist | From 6.0.0 | 6.0.20 | | `symfony/symfony` | Packagist | From 6.1.0 | 6.1.12 | | `symfony/symfony` | Packagist | From 6.1.0 | 6.1.12 | | `symfony/symfony` | Packagist | From 6.2.0 | 6.2.6 | | `symfony/symfony` | Packagist | From 6.2.0 | 6.2.6 | Products: Sensiolabs Symfony. ## How do I fix CVE-2022-24895? Upgrade symfony/security-bundle to a fixed version for your release line: 4.4.50, 5.4.20, 6.0.20 or 6.1.12. ## Is CVE-2022-24895 being exploited? There is no known exploitation of CVE-2022-24895 in the wild and no public exploit code. ## Other vulnerabilities in Sensiolabs Symfony - [CVE-2019-11325](https://insights.sbomify.com/CVE-2019-11325/): Improper Input Validation in Symfony (critical 9.8) - [CVE-2017-11365](https://insights.sbomify.com/CVE-2017-11365/): Symfony Incorrect Access Control (critical 9.8) - [CVE-2019-10913](https://insights.sbomify.com/CVE-2019-10913/): Invalid HTTP method overrides allow possible XSS or other attacks in Symfony (critical 9.8) - [CVE-2018-11407](https://insights.sbomify.com/CVE-2018-11407/): Symfony Authentication Bypass (critical 9.8) - [CVE-2016-2403](https://insights.sbomify.com/CVE-2016-2403/): Symfony Authentication Bypass (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-24895 and fix it if it is affected. What it is: CVE-2022-24895 is a medium-severity vulnerability in Sensiolabs Symfony, published on 3 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2022-24895 in the wild and no public exploit code. Affected packages and fixed versions: - symfony/security-bundle (Packagist): affected from 2.0.0; fixed in 4.4.50 - symfony/security-bundle (Packagist): affected from 2.0.0; fixed in 4.4.50 - symfony/security-bundle (Packagist): affected from 5.0.0; fixed in 5.4.20 - symfony/security-bundle (Packagist): affected from 5.0.0; fixed in 5.4.20 - symfony/security-bundle (Packagist): affected from 6.0.0; fixed in 6.0.20 - symfony/security-bundle (Packagist): affected from 6.0.0; fixed in 6.0.20 - symfony/security-bundle (Packagist): affected from 6.1.0; fixed in 6.1.12 - symfony/security-bundle (Packagist): affected from 6.1.0; fixed in 6.1.12 - symfony/security-bundle (Packagist): affected from 6.2.0; fixed in 6.2.6 - symfony/security-bundle (Packagist): affected from 6.2.0; fixed in 6.2.6 - symfony (Bitnami): affected from 2.0.0; fixed in 4.4.50, 5.4.20, 6.0.20, 6.1.12, 6.2.6 - symfony/symfony (Packagist): affected from 2.0.0; fixed in 4.4.50 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-24895/ (Markdown: https://insights.sbomify.com/CVE-2022-24895/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24895 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24895 - OSV: https://osv.dev/vulnerability/CVE-2022-24895 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-24895/ Summaries are generated and may contain mistakes; the official description above is the record.