Prevent cache poisoning via a Response Content-Type header
symfony
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/http-foundation Packagist |
|
|
| symfony/symfony Packagist |
|
symfony
| Product | Affected | Fixed in |
|---|---|---|
| symfony/http-foundation Packagist |
|
|
| symfony/symfony Packagist |
|
|
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.
From the CVE record · GitHub_M
In affected Symfony versions, a response without a Content-Type header can fall back to the format in the request’s Accept header, creating a mismatch between the content and header. If that response is cached, it can prevent other users from using the website. The input does not specify authentication or user-interaction requirements.
Teams running Packagist symfony/http-foundation or symfony/symfony versions >=4.4.0 <4.4.7 or >=5.0.0 <5.0.7 should check their installations.