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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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 relies on the presence of the package as reported by the vendor.

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.

According to its self-reported version number, the version of JFrog Artifactory installed on the remote host is prior to 7.11.1. It is, therefore, affected by multiple vulnerabilities:

  - A flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly.
    This flaw allows vulnerability to XML external entity (XXE) attacks. The highest threat from this vulnerability     is data integrity. (CVE-2020-25649)   
  - Plexus-utils before 3.0.16 is vulnerable to command injection because it does not correctly process the contents     of double quoted strings. (CVE-2017-1000487)

  - 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 Hazelcast before 3.11, the cluster join procedure is vulnerable to remote code execution via Java     deserialization. If an attacker can reach a listening Hazelcast instance with a crafted JoinRequest, and vulnerable     classes exist in the classpath, the attacker can run arbitrary code. (CVE-2016-10750)

Note that Nessus has not tested for this issue 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	Type	Severity
423486	SCA: security update for org.eclipse.jetty:jetty-server (GHSA-vgg8-72f2-qm23)	Tenable Cloud Security	SCA Checks	Local	critical
423486	SCA: security update for org.eclipse.jetty:jetty-server (GHSA-vgg8-72f2-qm23)	Tenable Self-Hosted Container Security	SCA Checks	Local	critical
221798	Linux Distros Unpatched Vulnerability : CVE-2017-7657	Nessus	Misc.	Local	critical
159514	F5 Networks BIG-IP : Eclipse Jetty vulnerabilities (K10002140)	Nessus	F5 Networks Local Security Checks	Local	critical
144306	JFrog < 7.11.1 Multiple Vulnerabilities	Nessus	Misc.	Local	critical
120388	Fedora 28 : jetty (2018-48b73ed393)	Nessus	Fedora Local Security Checks	Local	critical
111987	Debian DSA-4278-1 : jetty9 - security update	Nessus	Debian Local Security Checks	Local	critical
111048	Fedora 27 : jetty (2018-93a507fd0f)	Nessus	Fedora Local Security Checks	Local	critical

Detections

Analytics

CVE-2017-7657

critical

Tenable Plugins

critical

critical

critical

critical

critical

critical

critical

critical