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

Dependencies

(41 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.01.1.0up to date
 http^0.20.2.6up to date
 mime_guess^2.02.0.3up to date
 serde^1.01.0.135up to date
 serde_json^1.01.0.78up to date
 serde_urlencoded^0.70.7.1up to date
 url^2.22.2.2up to date
 async-compression^0.3.70.3.8up to date
 base64^0.130.13.0up to date
 cookie^0.150.16.0out of date
 cookie_store^0.150.15.1up to date
 encoding_rs^0.80.8.30up to date
 futures-core^0.3.00.3.19up to date
 futures-util^0.3.00.3.19up to date
 http-body^0.4.00.4.4up to date
 hyper ⚠️^0.140.14.16maybe insecure
 hyper-rustls^0.230.23.0up to date
 hyper-tls^0.50.5.0up to date
 ipnet^2.32.3.1up to date
 lazy_static^1.41.4.0up to date
 log^0.40.4.14up to date
 mime^0.3.160.3.16up to date
 native-tls^0.2.80.2.8up to date
 percent-encoding^2.12.1.0up to date
 pin-project-lite^0.2.00.2.8up to date
 proc-macro-hack^0.5.190.5.19up to date
 rustls^0.200.20.2up to date
 rustls-native-certs^0.60.6.1up to date
 rustls-pemfile^0.20.2.1up to date
 tokio ⚠️^1.01.15.0maybe insecure
 tokio-native-tls^0.3.00.3.0up to date
 tokio-rustls^0.230.23.2up to date
 tokio-socks^0.5.10.5.1up to date
 tokio-util^0.6.00.6.9up to date
 trust-dns-resolver^0.200.20.3up to date
 webpki-roots^0.210.22.2out of date
 js-sys^0.3.450.3.56up to date
 wasm-bindgen^0.2.680.2.79up to date
 wasm-bindgen-futures^0.4.180.4.29up to date
 web-sys^0.3.250.3.56up to date
 winreg^0.70.10.1out of date

Dev dependencies

(9 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 brotli^3.3.03.3.3up to date
 doc-comment^0.30.3.3up to date
 env_logger^0.80.9.0out of date
 hyper ⚠️^0.140.14.16maybe insecure
 libflate^1.01.1.2up to date
 serde^1.01.0.135up to date
 tokio ⚠️^1.01.15.0maybe insecure
 wasm-bindgen^0.2.680.2.79up to date
 wasm-bindgen-test^0.30.3.29up to date

Security Vulnerabilities

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.