Deps.rs

smol 0.1.18

[![dependency status](https://deps.rs/crate/smol/0.1.18/status.svg)](https://deps.rs/crate/smol/0.1.18)

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 smol

Dependencies

(14 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-task^3.0.04.7.1out of date
 blocking^0.4.61.6.0out of date
 concurrent-queue^1.1.12.5.0out of date
 fastrand^1.1.02.1.0out of date
 futures-io^0.3.50.3.30up to date
 futures-util^0.3.50.3.30up to date
 libc^0.2.700.2.154up to date
 once_cell^1.3.11.19.0up to date
 scoped-tls^1.0.01.0.1up to date
 slab^0.4.20.4.9up to date
 socket2^0.3.120.5.7out of date
 tokio ⚠️^0.21.37.0out of date
 wepoll-sys-stjepang^1.0.01.0.8up to date
 winapi^0.3.80.3.9up to date

Dev dependencies

(5 total, 2 outdated)

CrateRequiredLatestStatus
 criterion^0.30.5.1out of date
 futures^0.3.50.3.30up to date
 num_cpus^1.13.01.16.0up to date
 piper^0.1.20.2.1out of date
 tempfile^3.1.03.10.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.