Symfony HTTP Foundation web cache poisoning
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/http-foundation Packagist |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| symfony/http-foundation Packagist |
|
|
3.3.183.4.144.0.144.1.3| symfony/symfony Packagist |
|
|
An issue was discovered in Http Foundation in Symfony 2.7.0 through 2.7.48, 2.8.0 through 2.8.43, 3.3.0 through 3.3.17, 3.4.0 through 3.4.13, 4.0.0 through 4.0.13, and 4.1.0 through 4.1.2. It arises from support for a (legacy) IIS header that lets users override the path in the request URL via the X-Original-URL or X-Rewrite-URL HTTP request header. These headers are designed for IIS support, but it's not verified that the server is in fact running IIS, which means anybody who can send these requests to an application can trigger this. This affects \Symfony\Component\HttpFoundation\Request::prepareRequestUri() where X-Original-URL and X_REWRITE_URL are both used. The fix drops support for these methods so that they cannot be used as attack vectors such as web cache poisoning.
From the CVE record · mitre
Symfony Http Foundation accepts legacy IIS request headers that can override the path in a request URL without checking whether the server runs IIS. Anyone who can send HTTP requests to an affected application can trigger this behavior, creating an attack vector for web cache poisoning.
Teams running Packagist packages symfony/http-foundation or symfony/symfony in affected 2.7, 2.8, 3.0–3.3, 3.4, 4.0, or 4.1 releases should check their installed versions.