symfony/http-foundation
Affected
- introduced
4.4.0, fixed4.4.7(ecosystem)
Fixed versions
4.4.7
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-symfony-2020-5255, CVE-2020-5255
Prevent cache poisoning via a Response Content-Type header in Symfony
Description
-----------
When a Response does not contain a Content-Type header, Symfony falls back to the format defined in the Accept header of the request, leading to a possible mismatch between the response's content and Content-Type header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.
Resolution
----------
Symfony does not use the Accept header anymore to guess the Content-Type.
The patch for this issue is available here for the 4.4 branch.
Credits
-------
I would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.
Low Basis: The source's own band: LOW
4.4.0, fixed 4.4.7 (ecosystem)4.4.7
The export has no generic command for this ecosystem.
5.0.0, fixed 5.0.7 (ecosystem)5.0.7
The export has no generic command for this ecosystem.
4.4.0, fixed 4.4.7 (ecosystem)4.4.7
The export has no generic command for this ecosystem.
5.0.0, fixed 5.0.7 (ecosystem)5.0.7
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0