# CVE-2022-24894: Symfony storing cookie headers in HttpCache > Attackers can retrieve victim session cookies via cached responses in Symfony's HTTP cache system, potentially leading to account takeover. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **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-24894, CLSA-2026-1783386143, DEBIAN-CVE-2022-24894, GHSA-h7vf-5wrv-9fhv, UBUNTU-CVE-2022-24894 ## What is CVE-2022-24894? CVE-2022-24894 is a medium-severity vulnerability in Sensiolabs Symfony, published on 3 Feb 2023. Any signed-in user can exploit it over the network, 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. The Symfony HTTP cache system, acts as a reverse proxy: It caches entire responses (including headers) and returns them to the clients. In a recent change in the `AbstractSessionListener`, the response might contain a `Set-Cookie` header. If the Symfony HTTP cache system is enabled, this response might bill stored and return to the next clients. An attacker can use this vulnerability to retrieve the victim's session. This issue has been patched and is available for branch 4.4. Weakness: CWE-285 (Improper Authorization) ## Which versions are affected by CVE-2022-24894? 21 open source packages ship an affected version, including symfony/http-kernel, symfony and symfony/symfony. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `symfony/http-kernel` | Packagist | From 2.0.0 | 4.4.50 | | `symfony/http-kernel` | Packagist | From 2.0.0 | 4.4.50 | | `symfony/http-kernel` | Packagist | From 5.0.0 | 5.4.20 | | `symfony/http-kernel` | Packagist | From 5.0.0 | 5.4.20 | | `symfony/http-kernel` | Packagist | From 6.0.0 | 6.0.20 | | `symfony/http-kernel` | Packagist | From 6.0.0 | 6.0.20 | | `symfony/http-kernel` | Packagist | From 6.1.0 | 6.1.12 | | `symfony/http-kernel` | Packagist | From 6.1.0 | 6.1.12 | | `symfony/http-kernel` | Packagist | From 6.2.0 | 6.2.6 | | `symfony/http-kernel` | Packagist | From 6.2.0 | 6.2.6 | | `symfony` | Bitnami | From 2.0.0 | 4.4.50, 5.4.2, 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-24894? Upgrade symfony/http-kernel to a fixed version for your release line: 4.4.50, 5.4.20, 6.0.20 or 6.1.12. ## Is CVE-2022-24894 being exploited? There is no known exploitation of CVE-2022-24894 in the wild and no public exploit code. Public exploit code: - CVE-2021-21424 - CRLF Injection - CVE-2021-41268 - Host Header Injection - CVE-2022-24894 - WebProfiler abierto - CVE-2019-10909 - Directory Traversal (github_poc): https://github.com/moften/Symfony-CVE-Scanner-PoC- ## 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-24894 and fix it if it is affected. What it is: CVE-2022-24894 is a medium-severity vulnerability in Sensiolabs Symfony, published on 3 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2022-24894 in the wild and no public exploit code. Affected packages and fixed versions: - symfony/http-kernel (Packagist): affected from 2.0.0; fixed in 4.4.50 - symfony/http-kernel (Packagist): affected from 2.0.0; fixed in 4.4.50 - symfony/http-kernel (Packagist): affected from 5.0.0; fixed in 5.4.20 - symfony/http-kernel (Packagist): affected from 5.0.0; fixed in 5.4.20 - symfony/http-kernel (Packagist): affected from 6.0.0; fixed in 6.0.20 - symfony/http-kernel (Packagist): affected from 6.0.0; fixed in 6.0.20 - symfony/http-kernel (Packagist): affected from 6.1.0; fixed in 6.1.12 - symfony/http-kernel (Packagist): affected from 6.1.0; fixed in 6.1.12 - symfony/http-kernel (Packagist): affected from 6.2.0; fixed in 6.2.6 - symfony/http-kernel (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.2, 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-24894/ (Markdown: https://insights.sbomify.com/CVE-2022-24894/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24894 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24894 - OSV: https://osv.dev/vulnerability/CVE-2022-24894 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-24894/ Summaries are generated and may contain mistakes; the official description above is the record.