Denial of Service (DoS) Affecting apache/brpc package, versions [,1.14.1)

Affected versions of this package are vulnerable to Denial of Service (DoS) via the Redis protocol parser, which allocates memory for arrays or strings of corresponding sizes based on the integers read from the network. An attacker can cause the service to crash by sending specially crafted network packets that trigger excessive memory allocation, potentially leading to resource exhaustion and service interruption.

Note: This is exploitable if the service is configured to accept network connections from untrusted clients or interacts with untrusted Redis services.

This vulnerability can be mitigated by manually applying the patch available at https://github.com/apache/brpc/pull/3050, which limits the maximum memory allocation size in the Redis parser.

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

• Apache Thread
• GitHub Commit
• GitHub PR
• GitHub Release