Denial of Service (DoS) Affecting axum-core package, versions <0.2.8 >=0.3.0-rc.1 <0.3.0-rc.2

  • Attack Complexity


  • Availability


Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • snyk-id


  • published

    13 Sep 2022

  • disclosed

    31 Aug 2022

  • credit


How to fix?

Upgrade axum-core to version 0.2.8, 0.3.0-rc.2 or higher.


axum-core is an ergonomic and modular web framework built with Tokio, Tower, and Hyper

Affected versions of this package are vulnerable to Denial of Service (DoS) when Bytes::from_request calling hyper::body::into_bytes directly without setting a size limit for the request body. An attacker can send an infinite request body.


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