Webcache Poisoning in Symfony
symfony
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/http-kernel Packagist |
|
|
| symfony/symfony Packagist |
|
|
symfony
| Product | Affected | Fixed in |
|---|---|---|
| symfony/http-kernel Packagist |
|
|
| symfony/symfony Packagist |
|
|
Symfony/Http-Kernel is the HTTP kernel component for Symfony, a PHP framework for web and console applications and a set of reusable PHP components. Headers that are not part of the "trusted_headers" allowed list are ignored and protect users from "Cache poisoning" attacks. In Symfony 5.2, maintainers added support for the `X-Forwarded-Prefix` headers, but this header was accessible in SubRequest, even if it was not part of the "trusted_headers" allowed list. An attacker could leverage this opportunity to forge requests containing a `X-Forwarded-Prefix` header, leading to a web cache poisoning issue. Versions 5.3.12 and later have a patch to ensure that the `X-Forwarded-Prefix` header is not forwarded to subrequests when it is not trusted.
From the CVE record · GitHub_M
In affected Symfony versions, an untrusted X-Forwarded-Prefix header can reach subrequests even when it is not on the trusted_headers allowed list. An attacker can forge requests with this header to poison a web cache.
Check installations of Packagist symfony/http-kernel or symfony/symfony versions >=5.2.0 and <5.3.12.