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 bastion

Dependencies

(22 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.57up to date
 artillery-core^0.1.2-alpha.30.1.2up to date
 async-mutex^1.11.4.0up to date
 bastion-executor^0.4.20.4.2up to date
 crossbeam-queue^0.3.00.3.5up to date
 futures^0.3.50.3.21up to date
 futures-timer^3.0.23.0.2up to date
 fxhash^0.20.2.1up to date
 lasso^0.60.6.0up to date
 lazy_static^1.41.4.0up to date
 lever ⚠️^0.10.1.3maybe insecure
 lightproc^0.30.3.5up to date
 log^0.4.140.4.17up to date
 once_cell^1.7.21.10.0up to date
 pin-utils^0.10.1.0up to date
 serde^1.01.0.137up to date
 serde_json^1.01.0.81up to date
 thiserror^1.0.241.0.31up to date
 tracing^0.1.150.1.34up to date
 tracing-subscriber^0.30.3.11up to date
 uuid^0.81.0.0out of date
 nuclei^0.10.2.0out of date

Dev dependencies

(10 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bastion-utils^0.3.20.3.2up to date
 env_logger^0.90.9.0up to date
 num_cpus^1.13.01.13.1up to date
 once_cell^1.5.21.10.0up to date
 proptest^1.01.0.0up to date
 rand^0.80.8.5up to date
 rayon^1.3.11.5.2up to date
 snap^1.01.0.5up to date
 tokio ⚠️^1.11.18.2maybe insecure
 tokio-test^0.4.00.4.2up to date

Security Vulnerabilities

lever: AtomicBox<T> lacks bound on its Send and Sync traits allowing data races

RUSTSEC-2020-0137

AtomicBox<T> is a Box type designed to be used across threads, however, it implements the Send and Sync traits for all types T.

This allows non-Send types such as Rc and non-Sync types such as Cell to be used across thread boundaries which can trigger undefined behavior and memory corruption.

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.