Denial of Service (DoS) Affecting tokio-rustls package, versions >=0.12.0 <0.12.3>=0.13.0 <0.13.1


Severity

Recommended
0.0
medium
0
10

CVSS assessment made by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.1% (44th percentile)

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 Learn

Learn about Denial of Service (DoS) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RUST-TOKIORUSTLS-575025
  • published1 Jul 2020
  • disclosed19 May 2020
  • creditUnknown

Introduced: 19 May 2020

CVE-2020-35875  (opens in a new tab)
CWE-400  (opens in a new tab)

How to fix?

Upgrade tokio-rustls to version 0.12.3, 0.13.1 or higher.

Overview

tokio-rustls is an Asynchronous TLS/SSL streams for Tokio using Rustls.

Affected versions of this package are vulnerable to Denial of Service (DoS). It does not call process_new_packets immediately after read, so the expected termination condition wants_read always returns true. As long as new incoming data arrives faster than it is processed and the reader does not return pending, data will be buffered. This may cause DoS.

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

References

CVSS Scores

version 3.1