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.
hyper(21 total, 9 outdated, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes | ^0.4.6 | 1.8.0 | out of date |
| futures | ^0.1.21 | 0.3.31 | out of date |
| futures-cpupool | ^0.1.6 | 0.1.8 | up to date |
| h2 ⚠️ | ^0.1.13 | 0.4.6 | out of date |
| http ⚠️ | ^0.1.15 | 1.1.0 | out of date |
| http-body | ^0.1 | 1.0.1 | out of date |
| httparse | ^1.0 | 1.9.5 | up to date |
| iovec | ^0.1 | 0.1.4 | up to date |
| itoa | ^0.4.1 | 1.0.11 | out of date |
| log | ^0.4 | 0.4.22 | up to date |
| net2 | ^0.2.32 | 0.2.39 | up to date |
| time ⚠️ | ^0.1 | 0.3.36 | out of date |
| tokio ⚠️ | ^0.1.14 | 1.41.0 | out of date |
| tokio-buf | ^0.1 | 0.1.1 | up to date |
| tokio-executor | ^0.1.0 | 0.1.10 | up to date |
| tokio-io | ^0.1 | 0.1.13 | up to date |
| tokio-reactor | ^0.1 | 0.1.12 | up to date |
| tokio-tcp | ^0.1 | 0.1.4 | up to date |
| tokio-threadpool | ^0.1.16 | 0.1.18 | up to date |
| tokio-timer | ^0.2 | 0.2.13 | up to date |
| want | ^0.2 | 0.3.1 | out of date |
(10 total, 3 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-timer | ^0.1 | 3.0.3 | out of date |
| num_cpus | ^1.0 | 1.16.0 | up to date |
| pretty_env_logger | ^0.3 | 0.5.0 | out of date |
| serde | ^1.0 | 1.0.214 | up to date |
| serde_derive | ^1.0 | 1.0.214 | up to date |
| serde_json | ^1.0 | 1.0.132 | up to date |
| spmc | ^0.3 | 0.3.0 | up to date |
| tokio-fs | ^0.1 | 0.1.7 | up to date |
| tokio-mockstream | ^1.1.0 | 1.1.0 | up to date |
| url | ^1.0 | 2.5.3 | out of 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:
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.
h2: Resource exhaustion vulnerability in h2 may lead to Denial of Service (DoS)If an attacker is able to flood the network with pairs of HEADERS/RST_STREAM frames, such that the h2 application is not able to accept them faster than the bytes are received, the pending accept queue can grow in memory usage. Being able to do this consistently can result in excessive memory use, and eventually trigger Out Of Memory.
This flaw is corrected in hyperium/h2#668, which restricts remote reset stream count by default.
h2: Resource exhaustion vulnerability in h2 may lead to Denial of Service (DoS)An attacker with an HTTP/2 connection to an affected endpoint can send a steady stream of invalid frames to force the generation of reset frames on the victim endpoint. By closing their recv window, the attacker could then force these resets to be queued in an unbounded fashion, resulting in Out Of Memory (OOM) and high CPU usage.
This fix is corrected in hyperium/h2#737, which limits the total number of internal error resets emitted by default before the connection is closed.
h2: Degradation of service in h2 servers with CONTINUATION FloodAn attacker can send a flood of CONTINUATION frames, causing h2 to process them indefinitely.
This results in an increase in CPU usage.
Tokio task budget helps prevent this from a complete denial-of-service, as the server can still respond to legitimate requests, albeit with increased latency.
More details at "https://seanmonstar.com/blog/hyper-http2-continuation-flood/.
Patches available for 0.4.x and 0.3.x versions.