CVE-2019-18678

An issue was discovered in Squid 3.x and 4.x through 4.8. It allows attackers to smuggle HTTP requests through frontend software to a Squid instance that splits the HTTP Request pipeline differently. The resulting Response messages corrupt caches (between a client and Squid) with attacker-controlled content at arbitrary URLs. Effects are isolated to software between the attacker client and Squid. There are no effects on Squid itself, nor on any upstream servers. The issue is related to a request header containing whitespace between a header name and a colon.

An issue was discovered in Squid 3.x and 4.x through 4.8. It allows attackers to smuggle HTTP requests through frontend software to a Squid instance that splits the HTTP Request pipeline differently. The resulting Response messages corrupt caches (between a client and Squid) with attacker-controlled content at arbitrary URLs. Effects are isolated to software between the attacker client and Squid. There are no effects on Squid itself, nor on any upstream servers. The issue is related to a request header containing whitespace between a header name and a colon.

Se descubrió un problema en Squid versiones 2.x, 3.x y versiones 4.x hasta 4.8. Permite a atacantes pasar un trafico no autorizado de peticiones HTTP mediante el software frontend e una instancia de Squid que divide la tubería de la petición HTTP de manera diferente. Los mensajes de respuesta resultantes corrompen las memorias caché (entre un cliente y Squid) con contenido controlado por el atacante en URL arbitrarias. Los efectos son aislados del software entre el cliente atacante y Squid. No existen efectos en Squid en sí, ni en ningún servidor ascendente. El problema está relacionado con un encabezado de petición que contiene espacios en blanco entre un nombre de encabezado y dos puntos.