CVE-2022-41881

Netty project is an event-driven asynchronous network application framework. In versions prior to 4.1.86.Final, a StackOverflowError can be raised when parsing a malformed crafted message due to an infinite recursion. This issue is patched in version 4.1.86.Final. There is no workaround, except using a custom HaProxyMessageDecoder.

Impact

A StackOverflowError can be raised when parsing a malformed crafted message due to an infinite recursion.

Patches

Users should upgrade to 4.1.86.Final.

Workarounds

There is no workaround, except using a custom HaProxyMessageDecoder.

References

When parsing a TLV with type = PP2_TYPE_SSL, the value can be again a TLV with type = PP2_TYPE_SSL and so on. The only limitation of the recursion is that the TLV length cannot be bigger than 0xffff because it is encoded in an unsigned short type. Providing a TLV with a nesting level that is large enough will lead to raising of a StackOverflowError. The StackOverflowError will be caught if HAProxyMessageDecoder is used as part of Netty’s ChannelPipeline, but using it directly without the ChannelPipeline will lead to a thrown exception / crash.

For more information

If you have any questions or comments about this advisory:

• Open an issue in netty

A client might overload the server by issue frequent RST frames. This can cause a massive amount of load on the remote system and so cause a DDOS attack.

Impact

This is a DDOS attack, any http2 server is affected and so you should update as soon as possible.

Patches

This is patched in version 4.1.100.Final.

Workarounds

A user can limit the amount of RST frames that are accepted per connection over a timeframe manually using either an own Http2FrameListener implementation or an ChannelInboundHandler implementation (depending which http2 API is used).

References

• https://www.cve.org/CVERecord?id=CVE-2023-44487
• https://blog.cloudflare.com/technical-breakdown-http2-rapid-reset-ddos-attack/
• https://cloud.google.com/blog/products/identity-security/google-cloud-mitigated-largest-ddos-attack-peaking-above-398-million-rps/

Asynchronous event-driven network application Java framework.

Security Fix(es):

Netty project is an event-driven asynchronous network application framework. In versions prior to 4.1.86.Final, a StackOverflowError can be raised when parsing a malformed crafted message due to an infinite recursion. This issue is patched in version 4.1.86.Final. There is no workaround, except using a custom HaProxyMessageDecoder.(CVE-2022-41881)

Asynchronous event-driven network application Java framework.

Security Fix(es):

Netty project is an event-driven asynchronous network application framework. In versions prior to 4.1.86.Final, a StackOverflowError can be raised when parsing a malformed crafted message due to an infinite recursion. This issue is patched in version 4.1.86.Final. There is no workaround, except using a custom HaProxyMessageDecoder.(CVE-2022-41881)

Asynchronous event-driven network application Java framework.

Security Fix(es):

Netty project is an event-driven asynchronous network application framework. In versions prior to 4.1.86.Final, a StackOverflowError can be raised when parsing a malformed crafted message due to an infinite recursion. This issue is patched in version 4.1.86.Final. There is no workaround, except using a custom HaProxyMessageDecoder.(CVE-2022-41881)

Security Fix(es):

Netty project is an event-driven asynchronous network application framework. In versions prior to 4.1.86.Final, a StackOverflowError can be raised when parsing a malformed crafted message due to an infinite recursion. This issue is patched in version 4.1.86.Final. There is no workaround, except using a custom HaProxyMessageDecoder.(CVE-2022-41881)

Security Fix(es):

Netty project is an event-driven asynchronous network application framework. In versions prior to 4.1.86.Final, a StackOverflowError can be raised when parsing a malformed crafted message due to an infinite recursion. This issue is patched in version 4.1.86.Final. There is no workaround, except using a custom HaProxyMessageDecoder.(CVE-2022-41881)

Security Fix(es):

Netty project is an event-driven asynchronous network application framework. In versions prior to 4.1.86.Final, a StackOverflowError can be raised when parsing a malformed crafted message due to an infinite recursion. This issue is patched in version 4.1.86.Final. There is no workaround, except using a custom HaProxyMessageDecoder.(CVE-2022-41881)

Root has patched GHSA-xpw8-rcwv-8f8p in the io.root.io.netty:netty-codec-http2 package for Root:Maven. Multiple fixed versions available.

Netty project is an event-driven asynchronous network application framework. In versions prior to 4.1.86.Final, a StackOverflowError can be raised when parsing a malformed crafted message due to an infinite recursion. This issue is patched in version 4.1.86.Final. There is no workaround, except using a custom HaProxyMessageDecoder.

TuxCare rebuilt 43 io.netty packages to address 12 CVEs. Fixed in 4.1.63.Final-tuxcare.2.

TuxCare rebuilt 40 io.netty packages to address 16 CVEs. Fixed in 4.1.52.Final-tuxcare.1.

TuxCare rebuilt 46 io.netty packages to address 6 CVEs. Fixed in 4.1.82.Final-tuxcare.1.

TuxCare rebuilt 6 io.netty packages to address 9 CVEs. Fixed in 4.1.58.Final-tuxcare.1.

TuxCare rebuilt 43 io.netty packages to address 15 CVEs. Fixed in 4.1.60.Final-tuxcare.1.

TuxCare rebuilt 46 io.netty packages to address 9 CVEs. Fixed in 4.1.75.Final-tuxcare.1.

TuxCare rebuilt 46 io.netty packages to address 6 CVEs. Fixed in 4.1.73.Final-tuxcare.1.

TuxCare rebuilt 4 io.netty packages to address 4 CVEs. Fixed in 4.1.48.Final-tuxcare.2.

TuxCare rebuilt 2 io.netty packages to address 2 CVEs. Fixed in 4.1.49.Final-tuxcare.3.

TuxCare rebuilt 7 io.netty packages to address 8 CVEs. Fixed in 4.1.79.Final-tuxcare.1.

TuxCare rebuilt 3 io.netty packages to address 4 CVEs. Fixed in 4.1.43.Final-tuxcare.1.

TuxCare rebuilt 46 io.netty packages to address 19 CVEs. Fixed in 4.1.80.Final-tuxcare.1.

TuxCare rebuilt 6 io.netty packages to address 13 CVEs. Fixed in 4.1.42.Final-tuxcare.1.

TuxCare rebuilt 40 io.netty packages to address 26 CVEs. Fixed in 4.1.53.Final-tuxcare.1.

TuxCare rebuilt 6 io.netty packages to address 11 CVEs. Fixed in 4.1.39.Final-tuxcare.1.

TuxCare rebuilt 11 io.netty packages to address 21 CVEs. Fixed in 4.1.51.Final-tuxcare.1.

TuxCare rebuilt 4 io.netty packages to address 6 CVEs. Fixed in 4.1.24.Final-tuxcare.1.

TuxCare rebuilt 4 io.netty packages to address 6 CVEs. Fixed in 4.1.29.Final-tuxcare.1.

TuxCare rebuilt 7 io.netty packages to address 10 CVEs. Fixed in 4.1.21.Final-tuxcare.1.

TuxCare rebuilt 6 io.netty packages to address 7 CVEs. Fixed in 4.1.31.Final-tuxcare.1.

TuxCare rebuilt 6 io.netty packages to address 8 CVEs. Fixed in 4.1.38.Final-tuxcare.1.

TuxCare rebuilt 6 io.netty packages to address 7 CVEs. Fixed in 4.1.23.Final-tuxcare.1.

TuxCare rebuilt io.netty:netty-codec-haproxy to address 2 CVEs. Fixed in 4.0.56.Final-tuxcare.2.

These are all security issues fixed in the netty-4.1.114-1.1 package on the GA media of openSUSE Tumbleweed.

This update for netty, netty-tcnative fixes the following issues:

netty:

• Security fixes included in this version update from 4.1.75 to 4.1.90:

  • CVE-2022-24823: Local Information Disclosure Vulnerability in Netty on Unix-Like systems due temporary files for Java 6 and lower in io.netty:netty-codec-http (bsc#1199338)
  • CVE-2022-41881: HAProxyMessageDecoder Stack Exhaustion DoS (bsc#1206360)
  • CVE-2022-41915: HTTP Response splitting from assigning header value iterator (bsc#1206379)

• Other non-security bug fixes included in this version update from 4.1.75 to 4.1.90:

  • Build with Java 11 on ix86 architecture in order to avoid build failures
  • Fix HttpHeaders.names for non-String headers
  • Fix FlowControlHandler behaviour to pass read events when auto-reading is turned off
  • Fix brotli compression
  • Fix a bug in FlowControlHandler that broke auto-read
  • Fix a potential memory leak bug has been in the pooled allocator
  • Fix a scalability issue caused by instanceof and check-cast checks that lead to false-sharing on the Klass::secondary_super_cache field in the JVM
  • Fix a bug in our PEMParser when PEM files have multiple objects, and BouncyCastle is on the classpath
  • Fix several NullPointerException bugs
  • Fix a regression SslContext private key loading
  • Fix a bug in SslContext private key reading fall-back path
  • Fix a buffer leak regression in HttpClientCodec
  • Fix a bug where some HttpMessage implementations, that also implement HttpContent, were not handled correctly
  • Fix epoll bug when receiving zero-sized datagrams
  • Fix a bug in SslHandler so handlerRemoved works properly even if handlerAdded throws an exception
  • Fix an issue that allowed the multicast methods on EpollDatagramChannel to be called outside of an event-loop thread
  • Fix a bug where an OPT record was added to DNS queries that already had such a record
  • Fix a bug that caused an error when files uploaded with HTTP POST contained a backslash in their name
  • Fix an issue in the BlockHound integration that could occasionally cause NetUtil to be reported as performing blocking operation. A similar BlockHound issue was fixed for the JdkSslContext
  • Fix a bug that prevented preface or settings frames from being flushed, when an HTTP2 connection was established with prior-knowledge
  • Fix a bug where Netty fails to load a shaded native library
  • Fix and relax overly strict HTTP/2 header validation check that was rejecting requests from Chrome and Firefox
  • Fix OpenSSL and BoringSSL implementations to respect the jdk.tls.client.protocols and jdk.tls.server.protocols system properties, making them react to these in the same way the JDK SSL provider does
  • Fix inconsitencies in how epoll, kqueue, and NIO handle RDHUP
  • For a more detailed list of changes please consult the official release notes:
    • Changes from 4.1.90: https://netty.io/news/2023/03/14/4-1-90-Final.html
    • Changes from 4.1.89: https://netty.io/news/2023/02/13/4-1-89-Final.html
    • Changes from 4.1.88: https://netty.io/news/2023/02/12/4-1-88-Final.html
    • Changes from 4.1.87: https://netty.io/news/2023/01/12/4-1-87-Final.html
    • Changes from 4.1.86: https://netty.io/news/2022/12/12/4-1-86-Final.html
    • Changes from 4.1.85: https://netty.io/news/2022/11/09/4-1-85-Final.html
    • Changes from 4.1.84: https://netty.io/news/2022/10/11/4-1-84-Final.html
    • Changes from 4.1.82: https://netty.io/news/2022/09/13/4-1-82-Final.html
    • Changes from 4.1.81: https://netty.io/news/2022/09/08/4-1-81-Final.html
    • Changes from 4.1.80: https://netty.io/news/2022/08/26/4-1-80-Final.html
    • Changes from 4.1.79: https://netty.io/news/2022/07/11/4-1-79-Final.html
    • Changes from 4.1.78: https://netty.io/news/2022/06/14/4-1-78-Final.html
    • Changes from 4.1.77: https://netty.io/news/2022/05/06/2-1-77-Final.html
    • Changes from 4.1.76:…

This update for netty, netty-tcnative fixes the following issues:

netty:

• Security fixes included in this version update from 4.1.75 to 4.1.90:

  • CVE-2022-24823: Local Information Disclosure Vulnerability in Netty on Unix-Like systems due temporary files for Java 6 and lower in io.netty:netty-codec-http (bsc#1199338)
  • CVE-2022-41881: HAProxyMessageDecoder Stack Exhaustion DoS (bsc#1206360)
  • CVE-2022-41915: HTTP Response splitting from assigning header value iterator (bsc#1206379)

• Other non-security bug fixes included in this version update from 4.1.75 to 4.1.90:

  • Build with Java 11 on ix86 architecture in order to avoid build failures
  • Fix HttpHeaders.names for non-String headers
  • Fix FlowControlHandler behaviour to pass read events when auto-reading is turned off
  • Fix brotli compression
  • Fix a bug in FlowControlHandler that broke auto-read
  • Fix a potential memory leak bug has been in the pooled allocator
  • Fix a scalability issue caused by instanceof and check-cast checks that lead to false-sharing on the Klass::secondary_super_cache field in the JVM
  • Fix a bug in our PEMParser when PEM files have multiple objects, and BouncyCastle is on the classpath
  • Fix several NullPointerException bugs
  • Fix a regression SslContext private key loading
  • Fix a bug in SslContext private key reading fall-back path
  • Fix a buffer leak regression in HttpClientCodec
  • Fix a bug where some HttpMessage implementations, that also implement HttpContent, were not handled correctly
  • Fix epoll bug when receiving zero-sized datagrams
  • Fix a bug in SslHandler so handlerRemoved works properly even if handlerAdded throws an exception
  • Fix an issue that allowed the multicast methods on EpollDatagramChannel to be called outside of an event-loop thread
  • Fix a bug where an OPT record was added to DNS queries that already had such a record
  • Fix a bug that caused an error when files uploaded with HTTP POST contained a backslash in their name
  • Fix an issue in the BlockHound integration that could occasionally cause NetUtil to be reported as performing blocking operation. A similar BlockHound issue was fixed for the JdkSslContext
  • Fix a bug that prevented preface or settings frames from being flushed, when an HTTP2 connection was established with prior-knowledge
  • Fix a bug where Netty fails to load a shaded native library
  • Fix and relax overly strict HTTP/2 header validation check that was rejecting requests from Chrome and Firefox
  • Fix OpenSSL and BoringSSL implementations to respect the jdk.tls.client.protocols and jdk.tls.server.protocols system properties, making them react to these in the same way the JDK SSL provider does
  • Fix inconsitencies in how epoll, kqueue, and NIO handle RDHUP
  • For a more detailed list of changes please consult the official release notes:
    • Changes from 4.1.90: https://netty.io/news/2023/03/14/4-1-90-Final.html
    • Changes from 4.1.89: https://netty.io/news/2023/02/13/4-1-89-Final.html
    • Changes from 4.1.88: https://netty.io/news/2023/02/12/4-1-88-Final.html
    • Changes from 4.1.87: https://netty.io/news/2023/01/12/4-1-87-Final.html
    • Changes from 4.1.86: https://netty.io/news/2022/12/12/4-1-86-Final.html
    • Changes from 4.1.85: https://netty.io/news/2022/11/09/4-1-85-Final.html
    • Changes from 4.1.84: https://netty.io/news/2022/10/11/4-1-84-Final.html
    • Changes from 4.1.82: https://netty.io/news/2022/09/13/4-1-82-Final.html
    • Changes from 4.1.81: https://netty.io/news/2022/09/08/4-1-81-Final.html
    • Changes from 4.1.80: https://netty.io/news/2022/08/26/4-1-80-Final.html
    • Changes from 4.1.79: https://netty.io/news/2022/07/11/4-1-79-Final.html
    • Changes from 4.1.78: https://netty.io/news/2022/06/14/4-1-78-Final.html
    • Changes from 4.1.77: https://netty.io/news/2022/05/06/2-1-77-Final.html
    • Changes from 4.1.76:…

It was discovered that Netty's Zlib decoders did not limit memory allocations. A remote attacker could possibly use this issue to cause Netty to exhaust memory via malicious input, leading to a denial of service. This issue only affected Ubuntu 16.04 ESM and Ubuntu 20.04 ESM. (CVE-2020-11612)

It was discovered that Netty created temporary files with excessive permissions. A local attacker could possibly use this issue to expose sensitive information. This issue only affected Ubuntu 16.04 ESM, Ubuntu 18.04 ESM, and Ubuntu 20.04 ESM. (CVE-2021-21290)

It was discovered that Netty did not properly validate content-length headers. A remote attacker could possibly use this issue to smuggle requests. This issue was only fixed in Ubuntu 20.04 ESM. (CVE-2021-21295, CVE-2021-21409)

It was discovered that Netty's Bzip2 decompression decoder did not limit the decompressed output data size. A remote attacker could possibly use this issue to cause Netty to exhaust memory via malicious input, leading to a denial of service. This issue only affected Ubuntu 18.04 ESM, Ubuntu 20.04 ESM, Ubuntu 22.04 LTS, and Ubuntu 22.10. (CVE-2021-37136)

It was discovered that Netty's Snappy frame decoder function did not limit chunk lengths. A remote attacker could possibly use this issue to cause Netty to exhaust memory via malicious input, leading to a denial of service. (CVE-2021-37137)

It was discovered that Netty did not properly handle control chars at the beginning and end of header names. A remote attacker could possibly use this issue to smuggle requests. This issue only affected Ubuntu 18.04 ESM, Ubuntu 20.04 ESM, Ubuntu 22.04 LTS, and Ubuntu 22.10. (CVE-2021-43797)

It was discovered that Netty could be made into an infinite recursion when parsing a malformed crafted message. A remote attacker could possibly use this issue to cause Netty to crash, leading to a denial of service. This issue only affected Ubuntu 20.04 ESM, Ubuntu 22.04 LTS, and Ubuntu 22.10. (CVE-2022-41881)

It was discovered that Netty did not validate header values under certain circumstances. A remote attacker could possibly use this issue to perform HTTP response splitting via malicious header values. This issue only affected Ubuntu 18.04 ESM, Ubuntu 20.04 ESM, Ubuntu 22.04 LTS, and Ubuntu 22.10. (CVE-2022-41915)