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 actix

Dependencies

(18 total, 1 possibly insecure)

CrateRequiredLatestStatus
 actix-rt^2.0.02.5.0up to date
 actix_derive^0.6.00.6.0up to date
 bitflags^1.21.3.2up to date
 bytes^11.1.0up to date
 crossbeam-channel^0.50.5.1up to date
 futures-core^0.3.70.3.18up to date
 futures-sink^0.3.70.3.18up to date
 futures-task^0.3.70.3.18up to date
 futures-util^0.3.70.3.18up to date
 log^0.40.4.14up to date
 once_cell^1.51.8.0up to date
 parking_lot^0.110.11.2up to date
 pin-project-lite^0.20.2.7up to date
 smallvec^1.6.11.7.0up to date
 tokio ⚠️^11.14.0maybe insecure
 tokio-util^0.60.6.9up to date
 trust-dns-proto^0.20.00.20.3up to date
 trust-dns-resolver^0.20.00.20.3up 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.