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(16 total, 8 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes | ^0.5 | 1.9.0 | out of date |
| futures-channel | ^0.3 | 0.3.31 | up to date |
| futures-core | ^0.3 | 0.3.31 | up to date |
| futures-util | ^0.3 | 0.3.31 | up to date |
| h2 ⚠️ | ^0.2.2 | 0.4.7 | out of date |
| http | ^0.2 | 1.2.0 | out of date |
| http-body | ^0.3.1 | 1.0.1 | out of date |
| httparse | ^1.0 | 1.9.5 | up to date |
| httpdate | ^0.3 | 1.0.3 | out of date |
| itoa | ^0.4.1 | 1.0.14 | out of date |
| pin-project | ^1.0 | 1.1.7 | up to date |
| socket2 | ^0.3 | 0.5.8 | out of date |
| tokio ⚠️ | ^0.2.11 | 1.42.0 | out of date |
| tower-service | ^0.3 | 0.3.3 | up to date |
| tracing | ^0.1 | 0.1.41 | up to date |
| want | ^0.3 | 0.3.1 | up to date |
(14 total, 6 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-util | ^0.3 | 0.3.31 | up to date |
| matches | ^0.1 | 0.1.10 | up to date |
| num_cpus | ^1.0 | 1.16.0 | up to date |
| pnet ⚠️ | ^0.25.0 | 0.35.0 | out of date |
| pretty_env_logger | ^0.4 | 0.5.0 | out of date |
| serde | ^1.0 | 1.0.216 | up to date |
| serde_derive | ^1.0 | 1.0.216 | up to date |
| serde_json | ^1.0 | 1.0.133 | up to date |
| spmc | ^0.3 | 0.3.0 | up to date |
| tokio ⚠️ | ^0.2.2 | 1.42.0 | out of date |
| tokio-test | ^0.2 | 0.4.4 | out of date |
| tokio-util | ^0.3 | 0.7.13 | out of date |
| tower-util | ^0.3 | 0.3.1 | up to date |
| url | ^1.0 | 2.5.4 | out of date |
pnet: Compiler optimisation for next_with_timeout in pnet::transport::IcmpTransportChannelIterator flaws to SEGFAULTAffected versions of this crate were optimized out by compiler, which caused dereference of uninitialized file descriptor which caused segfault.
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.