This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate tower-web

Dependencies

(29 total, 15 outdated, 4 possibly insecure)

CrateRequiredLatestStatus
 atoi=0.2.32.0.0out of date
 bytes^0.4.71.6.0out of date
 checked^0.5.00.5.0up to date
 chrono ⚠️^0.4.40.4.37maybe insecure
 flate2^1.0.21.0.28up to date
 futures^0.1.210.3.30out of date
 handlebars~1.0.35.1.2out of date
 headers^0.2.00.4.0out of date
 http ⚠️^0.1.71.1.0out of date
 hyper ⚠️^0.12.11.2.0out of date
 lazy_static^11.4.0up to date
 log^0.4.10.4.21up to date
 mime^0.3.130.3.17up to date
 mime_guess^12.0.4out of date
 percent-encoding^1.0.12.3.1out of date
 proc-macro-hack^0.4.00.5.20+deprecatedout of date
 serde^1.0.701.0.197up to date
 serde_derive^1.0.701.0.197up to date
 serde_json^1.0.241.0.115up to date
 serde_plain^0.3.01.0.2out of date
 serde_urlencoded^0.5.10.7.1out of date
 tokio ⚠️^0.1.61.36.0out of date
 tokio-async-await^0.1.40.1.7up to date
 tokio-fs^0.1.20.1.7up to date
 tokio-io^0.1.70.1.13up to date
 tokio-rustls^0.8.00.26.0out of date
 tower-service^0.1.00.3.2out of date
 tower-web-macros^0.3.20.3.5up to date
 void^1.0.21.0.2up to date

Dev dependencies

(2 total, 2 outdated)

CrateRequiredLatestStatus
 env_logger^0.5.120.11.3out of date
 rand^0.5.50.8.5out of date

Security Vulnerabilities

http: Integer Overflow in HeaderMap::reserve() can cause Denial of Service

RUSTSEC-2019-0033

HeaderMap::reserve() used usize::next_power_of_two() to calculate the increased capacity. However, next_power_of_two() silently overflows to 0 if given a sufficiently large number in release mode.

If the map was not empty when the overflow happens, the library will invoke self.grow(0) and start infinite probing. This allows an attacker who controls the argument to reserve() to cause a potential denial of service (DoS).

The flaw was corrected in 0.1.20 release of http crate.

http: HeaderMap::Drain API is unsound

RUSTSEC-2019-0034

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

hyper: Lenient `hyper` header parsing of `Content-Length` could allow request smuggling

RUSTSEC-2021-0078

hyper's HTTP header parser accepted, according to RFC 7230, illegal contents inside Content-Length headers. Due to this, upstream HTTP proxies that ignore the header may still forward them along if it chooses to ignore the error.

To be vulnerable, hyper must be used as an HTTP/1 server and using an HTTP proxy upstream that ignores the header's contents but still forwards it. Due to all the factors that must line up, an attack exploiting this vulnerability is unlikely.

hyper: Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss

RUSTSEC-2021-0079

When decoding chunk sizes that are too large, hyper's code would encounter an integer overflow. Depending on the situation, this could lead to data loss from an incorrect total size, or in rarer cases, a request smuggling attack.

To be vulnerable, you must be using hyper for any HTTP/1 purpose, including as a client or server, and consumers must send requests or responses that specify a chunk size greater than 18 exabytes. For a possible request smuggling attack to be possible, any upstream proxies must accept a chunk size greater than 64 bits.

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.