Bug 2167258 (CVE-2022-24894) - CVE-2022-24894 php-symfony: Prevent storing cookie headers in HttpCache
Summary: CVE-2022-24894 php-symfony: Prevent storing cookie headers in HttpCache
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2022-24894
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2167260 2167259
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-06 04:38 UTC by Sandipan Roy
Modified: 2023-02-10 00:36 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-10 00:36:50 UTC
Embargoed:


Attachments (Terms of Use)

Description Sandipan Roy 2023-02-06 04:38:32 UTC
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.

https://github.com/symfony/symfony/commit/d2f6322af9444ac5cd1ef3ac6f280dbef7f9d1fb
https://github.com/symfony/symfony/security/advisories/GHSA-h7vf-5wrv-9fhv

Comment 1 Sandipan Roy 2023-02-06 04:41:21 UTC
Created php-symfony tracking bugs for this issue:

Affects: epel-7 [bug 2167260]
Affects: fedora-all [bug 2167259]

Comment 2 Product Security DevOps Team 2023-02-10 00:36:48 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.