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 tower

Dependencies

(14 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-core^0.30.3.25up to date
 futures-util^0.30.3.25up to date
 hdrhistogram^7.07.5.2up to date
 indexmap^1.0.21.9.2up to date
 pin-project^11.0.12up to date
 pin-project-lite^0.2.70.2.9up to date
 rand^0.80.8.5up to date
 slab^0.40.4.7up to date
 tokio ⚠️^1.61.22.0maybe insecure
 tokio-stream^0.1.00.1.11up to date
 tokio-util^0.7.00.7.4up to date
 tower-layer^0.3.10.3.2up to date
 tower-service^0.3.10.3.2up to date
 tracing^0.1.20.1.37up to date

Dev dependencies

(10 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.30.3.25up to date
 hdrhistogram^7.07.5.2up to date
 http^0.20.2.8up to date
 lazy_static^1.4.01.4.0up to date
 pin-project-lite^0.2.70.2.9up to date
 tokio ⚠️^1.6.21.22.0maybe insecure
 tokio-stream^0.10.1.11up to date
 tokio-test^0.40.4.2up to date
 tower-test^0.40.4.0up to date
 tracing-subscriber^0.30.3.16up to 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.