symfony/http-kernel
Affected
- introduced
2.0.0, fixed2.3.19(ecosystem)
Fixed versions
2.3.19
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2014-5245
Symfony allows direct access of ESI URLs behind a trusted proxy
All 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony HttpKernel component are affected by this security issue. Your application is vulnerable only if the ESI feature is enabled and there is a proxy in front of the web application.
This issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.2 as it is not maintained anymore.
Description
When you enable the ESI feature and when you are using a proxy like Varnish that you configured as a trusted proxy, the FragmentHandler considered requests to render fragments as coming from a trusted source, even if the client was requesting them directly. Symfony can not distinguish between ESI requests done on behalf of the client by Varnish and faked fragment requests coming directly from the client.
To mitigate this issue, and for not-supported Symfony versions, you can use the following workaround in your Varnish configuration (/_fragment being the URL path prefix configured under the fragment setting of the framework bundle configuration):
Copy
sub vcl_recv {
if (req.restarts == 0 && req.url ~ "^/_fragment") {
error 400;
}
}
Resolution
We do not rely on trusted IPs anymore when validating a fragment request as all fragment URLs are now signed.
The patch for this issue is available here: https://github.com/symfony/symfony/pull/11831
High Basis: The source's own band: HIGH
2.0.0, fixed 2.3.19 (ecosystem)2.3.19
The export has no generic command for this ecosystem.
2.4.0, fixed 2.4.9 (ecosystem)2.4.9
The export has no generic command for this ecosystem.
2.5.0, fixed 2.5.4 (ecosystem)2.5.4
The export has no generic command for this ecosystem.
2.0.0, fixed 2.3.19 (ecosystem)2.3.19
The export has no generic command for this ecosystem.
2.4.0, fixed 2.4.9 (ecosystem)2.4.9
The export has no generic command for this ecosystem.
2.5.0, fixed 2.5.4 (ecosystem)2.5.4
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