NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Composer (PHP)

CVE-2014-5245: Symfony allows direct access of ESI URLs behind a trusted proxy

highCVSS 3.1 7.5GHSA-wvjv-p5rr-mmqm

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.

Published May 30, 2024

Affected packages

symfony/http-kernel

Ecosystem
Composer (PHP)
Affected
>= 2.0.0, < 2.3.19
Fixed in
2.3.19
Check
composer show symfony/http-kernel

symfony/http-kernel

Ecosystem
Composer (PHP)
Affected
>= 2.4.0, < 2.4.9
Fixed in
2.4.9
Check
composer show symfony/http-kernel

symfony/http-kernel

Ecosystem
Composer (PHP)
Affected
>= 2.5.0, < 2.5.4
Fixed in
2.5.4
Check
composer show symfony/http-kernel

symfony/symfony

Ecosystem
Composer (PHP)
Affected
>= 2.0.0, < 2.3.19
Fixed in
2.3.19
Check
composer show symfony/symfony

symfony/symfony

Ecosystem
Composer (PHP)
Affected
>= 2.4.0, < 2.4.9
Fixed in
2.4.9
Check
composer show symfony/symfony

symfony/symfony

Ecosystem
Composer (PHP)
Affected
>= 2.5.0, < 2.5.4
Fixed in
2.5.4
Check
composer show symfony/symfony

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Composer (PHP) vulnerabilities

All Composer (PHP) entries