Описание
Squid is a caching proxy for the Web. From 3.3.0.1 to before 7.6, due to an improper enforcement of behavioral workflow bug, Squid is vulnerable to a Request Smuggling attack against HTTP/1.1 Transfer-Encoding. HTTP header parsing (src/HttpHeader.cc) accepted the bare Transfer-Encoding: identity form, which the HTTP specification prohibits because any transfer coding must be wrapped within chunked encoding. This problem allows a trusted client to perform an HTTP Request Smuggling attack when HTTP/1.1 is used, bypassing security mechanisms that may be in place between attacker and Squid. When there is an HTTP cache operating prior to the affected Squid, this Request Smuggling attack also allows the attacker to poison that web cache and store arbitrary malicious content at any URL for delivery to other clients' future requests. This issue is fixed in version 7.6.
A flaw was found in Squid. Due to improper handling of HTTP/1.1 Transfer-Encoding headers, a trusted client can perform an HTTP request smuggling attack, interfering with how web requests are processed. This vulnerability allows an attacker to bypass intermediate security controls. When an HTTP cache operates in front of the affected Squid instance, the attacker can also poison that cache, causing it to store and deliver malicious content to other users.
Отчет
This vulnerability is rated as having an Important severity because it allows network clients to bypass proxy security controls and poison shared web caches without requiring administrative privileges. In deployments where Squid acts as an intermediary or accelerator alongside HTTP caching layers, request desynchronization caused by specially crafted HTTP/1.1 Transfer-Encoding headers can lead to widespread cache contamination affecting other users. While exploitation requires client access to the proxy service, the resulting integrity impact across shared infrastructure justifies the Important rating.
Меры по смягчению последствий
To mitigate this vulnerability, administrators should enforce rigorous server-side HTTP header validation by explicitly denying conflicting or ambiguous framing requests. In your squid.conf, this can be temporarily achieved by rejecting the problematic encoding outright using the directive request_header_access Transfer-Encoding deny all. Alternatively, administrators can neutralize the request smuggling attack vector entirely by disabling connection reuse with the settings client_persistent_connections off and server_persistent_connections off.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 6 | squid | Affected | ||
| Red Hat Enterprise Linux 6 | squid34 | Affected | ||
| Red Hat Enterprise Linux 7 | squid | Affected | ||
| Red Hat Enterprise Linux 10 | squid | Fixed | RHSA-2026:98643 | 11.11.2026 |
| Red Hat Enterprise Linux 10.2 Extended Update Support | squid | Fixed | RHSA-2026:99123 | 11.11.2026 |
| Red Hat Enterprise Linux 8 | squid | Fixed | RHSA-2026:96078 | 09.11.2026 |
| Red Hat Enterprise Linux 9 | squid | Fixed | RHSA-2026:98537 | 11.11.2026 |
| Red Hat Enterprise Linux 9.8 Extended Update Support | squid | Fixed | RHSA-2026:99124 | 12.11.2026 |
Показывать по
Дополнительная информация
Статус:
EPSS
7.7 High
CVSS3
Связанные уязвимости
Squid is a caching proxy for the Web. From 3.3.0.1 to before 7.6, due to an improper enforcement of behavioral workflow bug, Squid is vulnerable to a Request Smuggling attack against HTTP/1.1 Transfer-Encoding. HTTP header parsing (`src/HttpHeader.cc`) accepted the bare` Transfer-Encoding:` identity form, which the HTTP specification prohibits because any transfer coding must be wrapped within chunked encoding. This problem allows a trusted client to perform an HTTP Request Smuggling attack when HTTP/1.1 is used, bypassing security mechanisms that may be in place between attacker and Squid. When there is an HTTP cache operating prior to the affected Squid, this Request Smuggling attack also allows the attacker to poison that web cache and store arbitrary malicious content at any URL for delivery to other clients' future requests. This issue is fixed in version 7.6.
Squid is a caching proxy for the Web. From 3.3.0.1 to before 7.6, due to an improper enforcement of behavioral workflow bug, Squid is vulnerable to a Request Smuggling attack against HTTP/1.1 Transfer-Encoding. HTTP header parsing (`src/HttpHeader.cc`) accepted the bare` Transfer-Encoding:` identity form, which the HTTP specification prohibits because any transfer coding must be wrapped within chunked encoding. This problem allows a trusted client to perform an HTTP Request Smuggling attack when HTTP/1.1 is used, bypassing security mechanisms that may be in place between attacker and Squid. When there is an HTTP cache operating prior to the affected Squid, this Request Smuggling attack also allows the attacker to poison that web cache and store arbitrary malicious content at any URL for delivery to other clients' future requests. This issue is fixed in version 7.6.
Squid is a caching proxy for the Web. From 3.3.0.1 to before 7.6, due ...
EPSS
7.7 High
CVSS3