CVE-2022-24894 json
Symfony storing cookie headers in HttpCache
published 2023-02-01 3 y ago modified 2026-06-17 4 mo ago also BIT-symfony-2022-24894 , EUVD-2023-0715 , GHSA-h7vf-5wrv-9fhv
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.0%
- EPSS 4.0% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist symfony/http-kernel 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.2, 6.0.20, 6.1.12, 6.2.6
- sensiolabs symfony 4.4.50, 5.4.2, 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-24894
- 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-24894
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-24894 updated
php-symfony: Prevent storing cookie headers in HttpCache
-
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
4.00% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:L |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/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/http-kernel | >=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.2 >=6.0.0, <6.0.20 >=6.1.0, <6.1.12 >=6.2.0, <6.2.6 |
4.4.50 5.4.2 6.0.20 6.1.12 6.2.6 |
Affected products
- symfony symfony
Classification
- Weakness
-
- CWE-285 Improper Authorization
References
-
github.com
/symfony/symfony/commit/d2f6322af9444ac5cd1ef3ac6f280dbef7f9d1fb
web, patch
-
github.com
/symfony/symfony/security/advisories/GHSA-h7vf-5wrv-9fhv
web, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2023/07/msg00014.html
web, mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2022-24894
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/symfony/http-kernel/CVE-2022-24894.yaml
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2022-24894.yaml
web
-
github.com
/symfony/symfony
package
-
symfony.com
/cve-2022-24894
web
Sources
- CVE List CVE-2022-24894
- GitHub Advisory GHSA-h7vf-5wrv-9fhv
- NVD CVE-2022-24894
- OSV BIT-symfony-2022-24894
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.