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 hyper

Dependencies

(17 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.1.0up to date
 futures-channel^0.30.3.21up to date
 futures-core^0.30.3.21up to date
 futures-util^0.30.3.21up to date
 h2^0.3.90.3.13up to date
 http^0.20.2.8up to date
 http-body^0.40.4.5up to date
 httparse^1.61.7.1up to date
 httpdate^1.01.0.2up to date
 itoa^11.0.2up to date
 libc^0.20.2.126up to date
 pin-project-lite^0.2.40.2.9up to date
 socket2^0.40.4.4up to date
 tokio ⚠️^11.19.2maybe insecure
 tower-service^0.30.3.2up to date
 tracing^0.10.1.35up to date
 want^0.30.3.0up to date

Dev dependencies

(13 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-util^0.30.3.21up to date
 matches^0.10.1.9up to date
 num_cpus^1.01.13.1up to date
 pretty_env_logger^0.40.4.0up to date
 serde^1.01.0.138up to date
 serde_json^1.01.0.82up to date
 spmc^0.30.3.0up to date
 tokio ⚠️^11.19.2maybe insecure
 tokio-test^0.40.4.2up to date
 tokio-util^0.70.7.3up to date
 tower^0.40.4.13up to date
 url^2.22.2.2up to date
 pnet_datalink^0.27.20.31.0out of date

Security Vulnerabilities

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.