llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Packagist · symfony/http-kernel

GHSA-WVJV-P5RR-MMQM

Symfony allows direct access of ESI URLs behind a trusted proxy

Parche disponible
Descargar PNG JSON
CVSS
—
high
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche3 versiones2.3.19 · 2.4.9 · 2.5.4
Exposición904 dDesde la divulgación, 29 may 2024, 7:46 p. m.
Detección901 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Explotación
Remediación
Monitoreo
Detectada
30 may 24
17 nov 26
20 nov 26
30 may 24
11 ene 25
25 ago 25
8 abr 26
20 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-WVJV-P5RR-MMQM divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

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

Versiones

Rangos afectados

Afectada Corregida
symfony/http-kernel · symfony/symfony≥ 2.0.0 < 2.3.19
symfony/http-kernel · symfony/symfony≥ 2.4.0 < 2.4.9
symfony/http-kernel · symfony/symfony≥ 2.5.0 < 2.5.4
2.0.0
2.3.19
2.4.0
2.4.9
2.5.0
2.5.4
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Packagistsymfony/http-kernel
Corregida 2.3.19, 2.4.9, 2.5.4 — —
Packagistsymfony/symfony
Corregida 2.3.19, 2.4.9, 2.5.4 — —
Versiones corregidas2.3.192.4.92.5.4
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Otrahttps://github.com/symfony/symfony/pull/11831
Otrahttps://github.com/symfony/symfony/commit/654b1f281e09dd96ffbbd3da815411700423ecf5
Otrahttps://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/http-kernel/CVE-2014-5245.yaml
Otrahttps://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2014-5245.yaml
Otrahttps://symfony.com/cve-2014-5245

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.