Vulnerabilities

4 via 18 paths

Dependencies

13

Source

GitHub

Commit

c56bc960

Find, fix and prevent vulnerabilities in your code.

Severity
  • 2
  • 2
Status
  • 4
  • 0
  • 0

high severity

Denial of Service (DoS)

  • Vulnerable module: io.netty:netty-codec
  • Introduced through: io.lettuce:lettuce-core@6.1.0.RELEASE

Detailed paths

  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final io.netty:netty-codec@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.5.RELEASE.

Overview

io.netty:netty-codec is an event-driven asynchronous network application framework.

Affected versions of this package are vulnerable to Denial of Service (DoS). SnappyFrameDecoder doesn't restrict chunk length any mad buffer skippable chunks in an unnecessary way, leading to excessive memory usage. This vulnerability can be triggered by supplying malicious input that decompresses to a very big size (via a network stream or a file), or by sending a huge skippable chunk.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade io.netty:netty-codec to version 4.1.68.Final or higher.

References

high severity

Denial of Service (DoS)

  • Vulnerable module: io.netty:netty-codec
  • Introduced through: io.lettuce:lettuce-core@6.1.0.RELEASE

Detailed paths

  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final io.netty:netty-codec@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.5.RELEASE.

Overview

io.netty:netty-codec is an event-driven asynchronous network application framework.

Affected versions of this package are vulnerable to Denial of Service (DoS). Bzip2Decoder doesn't allow setting size restrictions for decompressed data. An attacker can exploit this by providing a compressed file that, when decompressed, triggers an out-of-memory exception.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade io.netty:netty-codec to version 4.1.68.Final or higher.

References

medium severity

Denial of Service (DoS)

  • Vulnerable module: io.netty:netty-handler
  • Introduced through: io.lettuce:lettuce-core@6.1.0.RELEASE

Detailed paths

  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.2.5.RELEASE.

Overview

io.netty:netty-handler is a library that provides an asynchronous event-driven network application framework and tools for rapid development of maintainable high performance and high scalability protocol servers and clients. In other words, Netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients. It greatly simplifies and streamlines network programming such as TCP and UDP socket server.

Affected versions of this package are vulnerable to Denial of Service (DoS) such that if the user has no idle timeout handler configured it might be possible for a remote peer to send a client hello packet which leads the server to buffer up to 16MB of data per connection.

The SniHandler class is a handler that waits for the TLS handshake to configure a SslHandler according to the indicated server name by the ClientHello record. For this matter it allocates a ByteBuf using the value defined in the ClientHello record.

Note:

An attacker can craft a packet that makes the SslClientHelloHandler to:

  1. Allocate a 16MB ByteBuf.

  2. Not fail decode method in buffer.

  3. Get out of the loop without an exception.

The combination of this without the use of a timeout makes it easy to connect to a TCP server and allocate 16MB of heap memory per connection.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade io.netty:netty-handler to version 4.1.94.Final or higher.

References

medium severity

Information Exposure

  • Vulnerable module: io.netty:netty-common
  • Introduced through: io.lettuce:lettuce-core@6.1.0.RELEASE

Detailed paths

  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-transport@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-transport@4.1.60.Final io.netty:netty-buffer@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final io.netty:netty-buffer@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-transport@4.1.60.Final io.netty:netty-resolver@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final io.netty:netty-resolver@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final io.netty:netty-transport@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final io.netty:netty-codec@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final io.netty:netty-transport@4.1.60.Final io.netty:netty-buffer@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final io.netty:netty-codec@4.1.60.Final io.netty:netty-buffer@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final io.netty:netty-transport@4.1.60.Final io.netty:netty-resolver@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final io.netty:netty-codec@4.1.60.Final io.netty:netty-transport@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final io.netty:netty-codec@4.1.60.Final io.netty:netty-transport@4.1.60.Final io.netty:netty-buffer@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.
  • Introduced through: RediSearch/lettusearch@RediSearch/lettusearch#c56bc960887af99d0b372dcbebfd7ef236fece36 io.lettuce:lettuce-core@6.1.0.RELEASE io.netty:netty-handler@4.1.60.Final io.netty:netty-codec@4.1.60.Final io.netty:netty-transport@4.1.60.Final io.netty:netty-resolver@4.1.60.Final io.netty:netty-common@4.1.60.Final
    Remediation: Upgrade to io.lettuce:lettuce-core@6.1.9.RELEASE.

Overview

Affected versions of this package are vulnerable to Information Exposure due to an incomplete fix to CVE-2021-21290, which still allowed one exploitable path. 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. Note: To be vulnerable, a victim application has to run on a Unix-like operating system, and with Java 6 or below.

Remediation

Upgrade io.netty:netty-common to version 4.1.77.Final or higher.

References