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.
bastion(22 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0 | 1.0.100 | up to date |
| artillery-core | ^0.1.2-alpha.3 | 0.1.2 | up to date |
| async-mutex | ^1.1 | 1.4.1 | up to date |
| bastion-executor | ^0.4.2 | 0.4.2 | up to date |
| crossbeam-queue | ^0.3.0 | 0.3.12 | up to date |
| futures | ^0.3.5 | 0.3.31 | up to date |
| futures-timer | ^3.0.2 | 3.0.3 | up to date |
| fxhash | ^0.2 | 0.2.1 | up to date |
| lasso | ^0.6 | 0.7.3 | out of date |
| lazy_static | ^1.4 | 1.5.0 | up to date |
| lever ⚠️ | ^0.1 | 0.1.4 | maybe insecure |
| lightproc | ^0.3 | 0.3.5 | up to date |
| log | ^0.4.14 | 0.4.28 | up to date |
| nuclei | ^0.1 | 0.4.4 | out of date |
| once_cell | ^1.7.2 | 1.21.3 | up to date |
| pin-utils | ^0.1 | 0.1.0 | up to date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.145 | up to date |
| thiserror | ^1.0.24 | 2.0.17 | out of date |
| tracing | ^0.1.15 | 0.1.41 | up to date |
| tracing-subscriber | ^0.3 | 0.3.20 | up to date |
| uuid | ^0.8 | 1.18.1 | out of date |
(10 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bastion-utils | ^0.3.2 | 0.3.2 | up to date |
| env_logger | ^0.9 | 0.11.8 | out of date |
| num_cpus | ^1.13.0 | 1.17.0 | up to date |
| once_cell | ^1.5.2 | 1.21.3 | up to date |
| proptest | ^1.0 | 1.9.0 | up to date |
| rand | ^0.8 | 0.9.2 | out of date |
| rayon | ^1.3.1 | 1.11.0 | up to date |
| snap | ^1.0 | 1.1.1 | up to date |
| tokio ⚠️ | ^1.1 | 1.48.0 | maybe insecure |
| tokio-test | ^0.4.0 | 0.4.4 | up to date |
lever: AtomicBox<T> lacks bound on its Send and Sync traits allowing data racesAtomicBox<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: reject_remote_clients Configuration corruptionOn Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.
This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.
The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.
Ensure that pipe_mode is set first after initializing a ServerOptions. For example:
let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);