In Eclipse Jetty Server, versions 9.2.x and older, 9.3.x (all non HTTP/1.x configurations), and 9.4.x (all HTTP/1.x configurations), when presented with two content-lengths headers, Jetty ignored the second. When presented with a content-length and a chunked encoding header, the content-length was ignored (as per RFC 2616). If an intermediary decided on the shorter length, but still passed on the longer body, then body content could be interpreted by Jetty as a pipelined request. If the intermediary was imposing authorization, the fake pipelined request would bypass that authorization.

The remote Redhat Enterprise Linux 6 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - jetty: Incorrect header handling (CVE-2017-7658)

  - 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. (CVE-2017-7656)

  - 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), transfer-encoding chunks are handled poorly. The chunk     length parsing was vulnerable to an integer overflow. Thus a large chunk size could be interpreted as a     smaller chunk size and content sent as chunk body could be interpreted as a pipelined request. If Jetty     was deployed behind an intermediary that imposed some authorization and that intermediary allowed     arbitrarily large chunks to be passed on unchanged, then this flaw could be used to bypass the     authorization imposed by the intermediary as the fake pipelined request would not be interpreted by the     intermediary as a request. (CVE-2017-7657)

Note that Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

The version of F5 Networks BIG-IP installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the K10002140 advisory.

  - 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), transfer-encoding chunks are handled poorly. The chunk     length parsing was vulnerable to an integer overflow. Thus a large chunk size could be interpreted as a     smaller chunk size and content sent as chunk body could be interpreted as a pipelined request. If Jetty     was deployed behind an intermediary that imposed some authorization and that intermediary allowed     arbitrarily large chunks to be passed on unchanged, then this flaw could be used to bypass the     authorization imposed by the intermediary as the fake pipelined request would not be interpreted by the     intermediary as a request. (CVE-2017-7657)

  - In Eclipse Jetty Server, versions 9.2.x and older, 9.3.x (all non HTTP/1.x configurations), and 9.4.x (all     HTTP/1.x configurations), when presented with two content-lengths headers, Jetty ignored the second. When     presented with a content-length and a chunked encoding header, the content-length was ignored (as per RFC     2616). If an intermediary decided on the shorter length, but still passed on the longer body, then body     content could be interpreted by Jetty as a pipelined request. If the intermediary was imposing     authorization, the fake pipelined request would bypass that authorization. (CVE-2017-7658)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Update to upstream version 9.4.11. Fixes CVE-2017-7656, CVE-2017-7657, CVE-2017-7658.

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Multiple vulnerabilities were discovered in Jetty, a Java servlet engine and webserver which could result in HTTP request smuggling.

Update to upstream version 9.4.11. Fixes CVE-2017-7656, CVE-2017-7657, CVE-2017-7658, CVE-2018-12538.

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
199780	RHEL 6 : nutch (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	critical
159514	F5 Networks BIG-IP : Eclipse Jetty vulnerabilities (K10002140)	Nessus	F5 Networks Local Security Checks	critical
120388	Fedora 28 : jetty (2018-48b73ed393)	Nessus	Fedora Local Security Checks	critical
111987	Debian DSA-4278-1 : jetty9 - security update	Nessus	Debian Local Security Checks	critical
111048	Fedora 27 : jetty (2018-93a507fd0f)	Nessus	Fedora Local Security Checks	critical

Detections

Analytics

CVE-2017-7658

critical

Tenable Plugins

critical

critical

critical

critical

critical