symfony/http-kernel
Affected
- introduced
5.2.0, fixed5.3.12(ecosystem)
Fixed versions
5.3.12
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-symfony-2021-41267, CVE-2021-41267
Webcache Poisoning in symfony/http-kernel
Description
-----------
When a Symfony application is running behind a proxy or a load-balancer, you can tell Symfony to look for the X-Forwarded-* HTTP headers. HTTP headers that are not part of the "trusted_headers" allowed list are ignored and protect you from "Cache poisoning" attacks.
In Symfony 5.2, we've added support for the X-Forwarded-Prefix header, but this header was accessible in sub-requests, 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 HTTP header, leading to a web cache poisoning issue.
Resolution
----------
Symfony now ensures that the X-Forwarded-Prefix HTTP header is not forwarded to sub-requests when it is not trusted.
The patch for this issue is available here for branch 5.3.
Credits
-------
We would like to thank Soner Sayakci for reporting the issue and Jérémy Derussé for fixing the issue.
Medium Basis: The source's own band: MODERATE
5.2.0, fixed 5.3.12 (ecosystem)5.3.12
The export has no generic command for this ecosystem.
5.2.0, fixed 5.3.12 (ecosystem)5.3.12
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0