View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004033||SymmetricDS||Improvement||public||2019-07-03 08:26||2019-07-03 08:27|
|Target Version||3.10.4||Fixed in Version||3.10.4|
|Summary||0004033: Upgrade the embedded Jetty to newest version|
|Description||The current version (9.4.7) of the embedded Jetty has several known CVE issues e.g.:|
[CVE-2017-7657] 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-7658] 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-2018-12536] In Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Error Handling, when an intentionally bad query arrives that doesn't match a dynamic url-pattern, and is eventually handled by the DefaultServlet's static file serving, the bad characters can trigger a java.nio.file.InvalidPathException which includes the full path to the base resource directory that the DefaultServlet and/or webapp is using. If this InvalidPathException is then handled by the default Error Handler, the InvalidPathException message is included in the error response, revealing the full server path to the requesting system.
[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), 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.
|2019-07-03 08:26||elong||New Issue|
|2019-07-03 08:26||elong||Status||new => assigned|
|2019-07-03 08:26||elong||Assigned To||=> elong|
|2019-07-03 08:26||elong||Relationship added||related to 0004032|
|2019-07-03 08:27||elong||Tag Attached: security|
|2019-07-03 08:27||elong||Status||assigned => resolved|
|2019-07-03 08:27||elong||Resolution||open => fixed|
|2019-07-03 08:27||elong||Fixed in Version||=> 3.10.4|