Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 710744 (CVE-2016-4970, CVE-2019-16869, CVE-2019-20444, CVE-2019-20445, CVE-2020-11612, CVE-2020-7238, CVE-2021-21290, CVE-2021-21295, CVE-2021-21409, CVE-2021-43797) - dev-java/netty-common: multiple vulnerabilities
Summary: dev-java/netty-common: multiple vulnerabilities
Status: RESOLVED INVALID
Alias: CVE-2016-4970, CVE-2019-16869, CVE-2019-20444, CVE-2019-20445, CVE-2020-11612, CVE-2020-7238, CVE-2021-21290, CVE-2021-21295, CVE-2021-21409, CVE-2021-43797
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Gentoo Security
URL:
Whiteboard: B3 [ebuild+ cve]
Keywords:
: 711186 (view as bug list)
Depends on: 827919
Blocks:
  Show dependency tree
 
Reported: 2020-02-25 00:34 UTC by GLSAMaker/CVETool Bot
Modified: 2022-01-09 09:36 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description GLSAMaker/CVETool Bot gentoo-dev 2020-02-25 00:34:41 UTC
CVE-2019-16869 (https://nvd.nist.gov/vuln/detail/CVE-2019-16869):
  Netty before 4.1.42.Final mishandles whitespace before the colon in HTTP
  headers (such as a "Transfer-Encoding : chunked" line), which leads to HTTP
  request smuggling.

CVE-2019-20444 (https://nvd.nist.gov/vuln/detail/CVE-2019-20444):
  ** RESERVED ** This candidate has been reserved by an organization or
  individual that will use it when announcing a new security problem. When the
  candidate has been publicized, the details for this candidate will be
  provided.

CVE-2019-20445 (https://nvd.nist.gov/vuln/detail/CVE-2019-20445):
  ** RESERVED ** This candidate has been reserved by an organization or
  individual that will use it when announcing a new security problem. When the
  candidate has been publicized, the details for this candidate will be
  provided.

CVE-2020-7238 (https://nvd.nist.gov/vuln/detail/CVE-2020-7238):
  Netty 4.1.43.Final allows HTTP Request Smuggling because it mishandles
  Transfer-Encoding whitespace (such as a [space]Transfer-Encoding:chunked
  line) and a later Content-Length header. This issue exists because of an
  incomplete fix for CVE-2019-16869.
Comment 1 Thomas Deutschmann gentoo-dev 2020-03-02 22:33:09 UTC
*** Bug 711186 has been marked as a duplicate of this bug. ***
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2020-04-08 21:14:01 UTC
* CVE-2020-11612

Description:
"The ZlibDecoders in Netty 4.1.x before 4.1.46 allow for unbounded memory allocation while decoding a ZlibEncoded byte stream. An attacker could send a large ZlibEncoded byte stream to the Netty server, forcing the server to allocate all of its free memory to a single decoder."

Bug: https://github.com/netty/netty/issues/6168
PR: https://github.com/netty/netty/pull/9924

Note that the bug mentions (https://github.com/netty/netty/issues/6168#issuecomment-580746140) that this may be an incomplete fix given other decoders have not been fixed in that change.
Comment 3 John Helmert III archtester Gentoo Infrastructure gentoo-dev Security 2021-02-09 04:54:30 UTC
CVE-2021-21290:

Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. In Netty before version 4.1.59.Final there is a vulnerability on Unix-like systems involving an insecure temp file. When netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. On unix-like systems, the temporary directory is shared between all user. As such, writing to this directory using APIs that do not explicitly set the file/directory permissions can lead to information disclosure. Of note, this does not impact modern MacOS Operating Systems. The method "File.createTempFile" on unix-like systems creates a random file, but, by default will create this file with the permissions "-rw-r--r--". Thus, if sensitive information is written to this file, other local users can read this information. This is the case in netty's "AbstractDiskHttpData" is vulnerable. This has been fixed in version 4.1.59.Final. As a workaround, one may specify your own "java.io.tmpdir" when you start the JVM or use "DefaultHttpDataFactory.setBaseDir(...)" to set the directory to something that is only readable by the current user.
Comment 4 John Helmert III archtester Gentoo Infrastructure gentoo-dev Security 2021-02-16 01:58:47 UTC
CVE-2016-4970:

handler/ssl/OpenSslEngine.java in Netty 4.0.x before 4.0.37.Final and 4.1.x before 4.1.1.Final allows remote attackers to cause a denial of service (infinite loop).
Comment 5 John Helmert III archtester Gentoo Infrastructure gentoo-dev Security 2021-03-10 13:48:49 UTC
CVE-2021-21295:

Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. In Netty (io.netty:netty-codec-http2) before version 4.1.60.Final there is a vulnerability that enables request smuggling. If a Content-Length header is present in the original HTTP/2 request, the field is not validated by `Http2MultiplexHandler` as it is propagated up. This is fine as long as the request is not proxied through as HTTP/1.1. If the request comes in as an HTTP/2 stream, gets converted into the HTTP/1.1 domain objects (`HttpRequest`, `HttpContent`, etc.) via `Http2StreamFrameToHttpObjectCodec `and then sent up to the child channel's pipeline and proxied through a remote peer as HTTP/1.1 this may result in request smuggling. In a proxy case, users may assume the content-length is validated somehow, which is not the case. If the request is forwarded to a backend channel that is a HTTP/1.1 connection, the Content-Length now has meaning and needs to be checked. An attacker can smuggle requests inside the body as it gets downgraded from HTTP/2 to HTTP/1.1. For an example attack refer to the linked GitHub Advisory. Users are only affected if all of this is true: `HTTP2MultiplexCodec` or `Http2FrameCodec` is used, `Http2StreamFrameToHttpObjectCodec` is used to convert to HTTP/1.1 objects, and these HTTP/1.1 objects are forwarded to another remote peer. This has been patched in 4.1.60.Final As a workaround, the user can do the validation by themselves by implementing a custom `ChannelInboundHandler` that is put in the `ChannelPipeline` behind `Http2StreamFrameToHttpObjectCodec`.
Comment 6 John Helmert III archtester Gentoo Infrastructure gentoo-dev Security 2021-04-05 01:16:45 UTC
CVE-2021-21409:

Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. In Netty (io.netty:netty-codec-http2) before version 4.1.61.Final there is a vulnerability that enables request smuggling. The content-length header is not correctly validated if the request only uses a single Http2HeaderFrame with the endStream set to to true. This could lead to request smuggling if the request is proxied to a remote peer and translated to HTTP/1.1. This is a followup of GHSA-wm47-8v5p-wjpj/CVE-2021-21295 which did miss to fix this one case. This was fixed as part of 4.1.61.Final.
Comment 7 John Helmert III archtester Gentoo Infrastructure gentoo-dev Security 2021-12-11 05:01:33 UTC
CVE-2021-43797:

Netty is an asynchronous event-driven network application framework for rapid
development of maintainable high performance protocol servers & clients. Netty prior to version 4.1.7.1.Final skips control chars when they are present at the beginning / end of the header name. It should instead fail fast as these are not allowed by the spec and could lead to HTTP request smuggling. Failing to do the validation might cause netty to "sanitize" header names before it forward these to another remote system when used as proxy. This remote system can't see the invalid usage anymore, and therefore does not do the validation itself. Users should upgrade to version 4.1.7.1.Final to receive a patch.
Comment 8 Volkmar W. Pogatzki 2021-12-27 11:11:25 UTC
According to what I can see in [1] all those CVEs do not affect the 'netty-common' component of netty.  Did I misread it?

[1] https://mvnrepository.com/artifact/io.netty/netty-all/4.1.42.Final
Comment 9 John Helmert III archtester Gentoo Infrastructure gentoo-dev Security 2022-01-09 09:36:08 UTC
(In reply to Volkmar W. Pogatzki from comment #8)
> According to what I can see in [1] all those CVEs do not affect the
> 'netty-common' component of netty.  Did I misread it?
> 
> [1] https://mvnrepository.com/artifact/io.netty/netty-all/4.1.42.Final

Perhaps not. Thanks!