In Symfony before versions 4.4.7 and 5.0.7, when a `Response` does not contain a `Content-Type` header, affected versions of Symfony can fallback 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 prevent the use of the website by other users. This has been patched in versions 4.4.7 and 5.0.7.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2020-0351 | In Symfony before versions 4.4.7 and 5.0.7, when a `Response` does not contain a `Content-Type` header, affected versions of Symfony can fallback 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 prevent the use of the website by other users. This has been patched in versions 4.4.7 and 5.0.7. |
Github GHSA |
GHSA-mcx4-f5f5-4859 | Prevent cache poisoning via a Response Content-Type header in Symfony |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2024-08-04T08:22:09.086Z
Reserved: 2020-01-02T00:00:00.000Z
Link: CVE-2020-5255
No data.
Status : Modified
Published: 2020-03-30T20:15:19.570
Modified: 2024-11-21T05:33:46.550
Link: CVE-2020-5255
No data.
OpenCVE Enrichment
No data.
EUVD
Github GHSA