~ / search / GHSA-mcx4-f5f5-4859

GHSA-mcx4-f5f5-4859

Prevent cache poisoning via a Response Content-Type header in Symfony

Source: GitHub Advisory Database (reviewed) Low CVE-2020-5255

Packages

EcosystemPackageAffectedFixed in
Packagist symfony/http-foundation >= 4.4.0, < 4.4.7 4.4.7
Packagist symfony/http-foundation >= 5.0.0, < 5.0.7 5.0.7
Packagist symfony/symfony >= 4.4.0, < 4.4.7 4.4.7
Packagist symfony/symfony >= 5.0.0, < 5.0.7 5.0.7

Details

As written in the advisory (Markdown source, shown as plain text).

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](https://github.com/symfony/symfony/commit/dca343442e6a954f96a2609e7b4e9c21ed6d74e6) 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.

References

External links from the advisory. They lead to third-party sites.