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 tracing-futures

Dependencies

(6 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 futures^0.10.3.21out of date
 futures-task ⚠️^0.30.3.21maybe insecure
 pin-project^1.01.0.10up to date
 tokio ⚠️^0.11.18.2out of date
 tokio-executor^0.10.1.10up to date
 tracing^0.10.1.34up to date

Dev dependencies

(3 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^0.1.221.18.2out of date
 tokio-test^0.20.4.2out of date
 tracing-core^0.1.20.1.26up to date

Security Vulnerabilities

futures-task: futures_task::waker may cause a use-after-free if used on a type that isn't 'static

RUSTSEC-2020-0060

Affected versions of the crate did not properly implement a 'static lifetime bound on the waker function. This resulted in a use-after-free if Waker::wake() is called after original data had been dropped.

The flaw was corrected by adding 'static lifetime bound to the data waker takes.

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.