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.
reqwest(33 total, 19 outdated, 5 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.10 | 0.22.1 | out of date |
| bytes | ^0.4 | 1.8.0 | out of date |
| cookie | ^0.12.0 | 0.18.1 | out of date |
| cookie_store | ^0.7.0 | 0.21.0 | out of date |
| encoding_rs | ^0.8 | 0.8.35 | up to date |
| flate2 | ^1.0.7 | 1.0.34 | up to date |
| futures | ^0.1.23 | 0.3.31 | out of date |
| http ⚠️ | ^0.1.15 | 1.1.0 | out of date |
| hyper ⚠️ | ^0.12.22 | 1.5.0 | out of date |
| hyper-old-types | ^0.11 | 0.11.0 | up to date |
| hyper-rustls | ^0.17.1 | 0.27.3 | out of date |
| hyper-tls | ^0.3.2 | 0.6.0 | out of date |
| log | ^0.4 | 0.4.22 | up to date |
| mime | ^0.3.7 | 0.3.17 | up to date |
| mime_guess | ^2.0 | 2.0.5 | up to date |
| native-tls | ^0.2 | 0.2.12 | up to date |
| rustls ⚠️ | ^0.16 | 0.23.16 | out of date |
| serde | ^1.0 | 1.0.214 | up to date |
| serde_json | ^1.0 | 1.0.132 | up to date |
| serde_urlencoded | ^0.5 | 0.7.1 | out of date |
| socks | ^0.3.2 | 0.3.4 | up to date |
| time ⚠️ | ^0.1.42 | 0.3.36 | out of date |
| tokio ⚠️ | ^0.1.7 | 1.41.0 | out of date |
| tokio-executor | ^0.1.4 | 0.1.10 | up to date |
| tokio-io | ^0.1 | 0.1.13 | up to date |
| tokio-rustls | ^0.10 | 0.26.0 | out of date |
| tokio-threadpool | ^0.1.8 | 0.1.18 | up to date |
| tokio-timer | ^0.2.6 | 0.2.13 | up to date |
| trust-dns-resolver | ^0.11 | 0.23.2 | out of date |
| url | ^1.2 | 2.5.3 | out of date |
| uuid | ^0.7 | 1.11.0 | out of date |
| webpki-roots | ^0.17 | 0.26.6 | out of date |
| winreg | ^0.6 | 0.52.0 | out of date |
(7 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes | ^0.4 | 1.8.0 | out of date |
| doc-comment | ^0.3 | 0.3.3 | up to date |
| env_logger | ^0.6 | 0.11.5 | out of date |
| libflate | ^0.1 | 2.1.0 | out of date |
| serde | ^1.0 | 1.0.214 | up to date |
| tokio ⚠️ | ^0.1.7 | 1.41.0 | out of date |
| tokio-tcp | ^0.1 | 0.1.4 | up to date |
http: Integer Overflow in HeaderMap::reserve() can cause Denial of ServiceHeaderMap::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 unsoundAffected versions of this crate incorrectly used raw pointer, which introduced unsoundness in its public safe API.
Failing to drop the Drain struct causes double-free, and it is possible to violate Rust's alias rule and cause data race with Drain's Iterator implementation.
The flaw was corrected in 0.1.20 release of http crate.
time: Potential segfault in the time crateThe affected functions set environment variables without synchronization. On Unix-like operating systems, this can crash in multithreaded programs. Programs may segfault due to dereferencing a dangling pointer if an environment variable is read in a different thread than the affected functions. This may occur without the user's knowledge, notably in the Rust standard library or third-party libraries.
The affected functions from time 0.2.7 through 0.2.22 are:
time::UtcOffset::local_offset_attime::UtcOffset::try_local_offset_attime::UtcOffset::current_local_offsettime::UtcOffset::try_current_local_offsettime::OffsetDateTime::now_localtime::OffsetDateTime::try_now_localThe affected functions in time 0.1 (all versions) are:
time::at_utctime::attime::nowtime::tzsetNon-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.
Cargo.toml:
chrono = { version = "0.4", default-features = false, features = ["serde"] }
chrono = { version = "0.4.22", default-features = false, features = ["clock"] }
Commandline:
cargo add chrono --no-default-features -F clock
Sources:
hyper: Lenient `hyper` header parsing of `Content-Length` could allow request smugglinghyper'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 lossWhen 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` channelIf 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.
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.