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 reqwest


(39 total, 19 outdated, 3 possibly insecure)

 async-compression^ of date
 base64^ of date
 bytes^ of date
 cookie^ of date
 cookie_store^ of date
 encoding_rs^ to date
 futures-core^ to date
 futures-util^ to date
 http^ of date
 http-body^ of date
 hyper ⚠️^ of date
 hyper-rustls^ of date
 hyper-tls^ of date
 ipnet^ to date
 js-sys^0.3.450.3.69up to date
 lazy_static^ to date
 log^ to date
 mime^ to date
 mime_guess^ to date
 native-tls^ to date
 percent-encoding^ to date
 pin-project-lite^ to date
 rustls^ of date
 rustls-native-certs^ of date
 serde^ to date
 serde_json^ to date
 serde_urlencoded^ to date
 time ⚠️^ of date
 tokio ⚠️^ of date
 tokio-rustls^ of date
 tokio-socks^ of date
 tokio-tls^ to date
 trust-dns-resolver^ of date
 url^ to date
 wasm-bindgen^0.2.680.2.92up to date
 wasm-bindgen-futures^ to date
 web-sys^ to date
 webpki-roots^ of date
 winreg^ of date

Dev dependencies

(8 total, 5 outdated, 2 possibly insecure)

 brotli^ of date
 doc-comment^ to date
 env_logger^ of date
 hyper ⚠️^ of date
 libflate^ of date
 serde^ to date
 tokio ⚠️^ of date
 wasm-bindgen-test^ to date

Security Vulnerabilities

time: Potential segfault in the time crate



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.

The affected functions from time 0.2.7 through 0.2.22 are:

  • time::UtcOffset::local_offset_at
  • time::UtcOffset::try_local_offset_at
  • time::UtcOffset::current_local_offset
  • time::UtcOffset::try_current_local_offset
  • time::OffsetDateTime::now_local
  • time::OffsetDateTime::try_now_local

The affected functions in time 0.1 (all versions) are:

  • at
  • at_utc
  • now

Non-Unix targets (including Windows and wasm) are unaffected.


Pending a proper fix, the internal method that determines the local offset has been modified to always return None on the affected operating systems. This has the effect of returning an Err on the try_* methods and UTC on the non-try_* methods.

Users and library authors with time in their dependency tree should perform cargo update, which will pull in the updated, unaffected code.

Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.


A possible workaround for crates affected through the transitive dependency in chrono, is to avoid using the default oldtime feature dependency of the chrono crate by disabling its default-features and manually specifying the required features instead.



chrono = { version = "0.4", default-features = false, features = ["serde"] }
chrono = { version = "0.4.22", default-features = false, features = ["clock"] }


cargo add chrono --no-default-features -F clock


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


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


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


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.