ALT-PU-2019-2113: package jetty update to version 9.4.11-alt1_3.v20180605jpp8
Описание
This update upgrades jetty to version 9.4.11-alt1_3.v20180605jpp8.
Устраненные уязвимости8
Ссылки5
GHSA-6x9x-8qw9-9pp6
https://github.com/advisories/GHSA-6x9x-8qw9-9pp6GHSA-84q7-p226-4x5w
https://github.com/advisories/GHSA-84q7-p226-4x5wGHSA-9rgv-h7x4-qw8g
https://github.com/advisories/GHSA-9rgv-h7x4-qw8gGHSA-vgg8-72f2-qm23
https://github.com/advisories/GHSA-vgg8-72f2-qm23Связанные уязвимости
In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), HTTP/0.9 is handled poorly. An HTTP/1 style request line (i.e. method space URI space version) that declares a version of HTTP/0.9 was accepted and treated as a 0.9 request. If deployed behind an intermediary that also accepted and passed through the 0.9 version (but did not act on it), then the response sent could be interpreted by the intermediary as HTTP/1 headers. This could be used to poison the cache if the server allowed the origin client to generate arbitrary content in the response.
In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), HTTP/0.9 is handled poorly. An HTTP/1 style request line (i.e. method space URI space version) that declares a version of HTTP/0.9 was accepted and treated as a 0.9 request. If deployed behind an intermediary that also accepted and passed through the 0.9 version (but did not act on it), then the response sent could be interpreted by the intermediary as HTTP/1 headers. This could be used to poison the cache if the server allowed the origin client to generate arbitrary content in the response.
In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), HTTP/0.9 is handled poorly. An HTTP/1 style request line (i.e. method space URI space version) that declares a version of HTTP/0.9 was accepted and treated as a 0.9 request. If deployed behind an intermediary that also accepted and passed through the 0.9 version (but did not act on it), then the response sent could be interpreted by the intermediary as HTTP/1 headers. This could be used to poison the cache if the server allowed the origin client to generate arbitrary content in the response.
In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations) ...
Jetty vulnerable to cache poisoning due to inconsistent HTTP request handling (HTTP Request Smuggling)