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 quinn

Dependencies

(11 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.2.1up to date
 futures-channel^0.3.110.3.24up to date
 futures-util^0.3.110.3.24up to date
 fxhash^0.2.10.2.1up to date
 quinn-proto^0.8.40.8.4up to date
 rustls^0.20.30.20.6up to date
 thiserror^1.0.211.0.37up to date
 tokio ⚠️^1.0.11.21.2maybe insecure
 tracing^0.1.100.1.36up to date
 quinn-udp^0.1.00.2.0out of date
 webpki^0.220.22.0up to date

Dev dependencies

(13 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.221.0.65up to date
 bencher^0.1.50.1.5up to date
 crc^23.0.0out of date
 directories-next^22.0.0up to date
 futures-util^0.3.110.3.24up to date
 rand^0.80.8.5up to date
 rcgen^0.80.10.0out of date
 rustls-pemfile^0.2.11.0.1out of date
 structopt^0.3.00.3.26up to date
 tokio ⚠️^1.0.11.21.2maybe insecure
 tracing-futures^0.2.00.2.5up to date
 tracing-subscriber^0.3.00.3.15up to date
 url^22.3.1up 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.