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 h2


(11 total, 1 possibly insecure)

 bytes^11.1.0up to date
 fnv^ to date
 futures-core^ to date
 futures-sink^ to date
 futures-util^ to date
 http^ to date
 indexmap^ to date
 slab^ to date
 tokio ⚠️^11.14.0maybe insecure
 tokio-util^ to date
 tracing^ to date

Dev dependencies

(12 total, 9 outdated, 1 possibly insecure)

 env_logger^ of date
 hex^ of date
 quickcheck^ of date
 rand^ of date
 rustls^ of date
 serde^ to date
 serde_json^ to date
 tokio ⚠️^11.14.0maybe insecure
 tokio-rustls^ of date
 walkdir^ of date
 webpki^ of date
 webpki-roots^ of date

Security Vulnerabilities

tokio: Data race when sending and receiving after closing a `oneshot` channel


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.