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-executor(17 total, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| arrayvec | ^0.7.0 | 0.7.8 | up to date |
| bastion-utils | ^0.3.2 | 0.3.2 | up to date |
| crossbeam-channel | ^0.5 | 0.5.16 | up to date |
| crossbeam-epoch ⚠️ | ^0.9 | 0.9.20 | maybe insecure |
| crossbeam-queue | ^0.3.0 | 0.3.13 | up to date |
| crossbeam-utils | ^0.8 | 0.8.22 | up to date |
| futures-timer | ^3.0.2 | 3.0.4 | up to date |
| lazy_static | ^1.4 | 1.5.0 | up to date |
| lever ⚠️ | ^0.1 | 0.1.4 | maybe insecure |
| libc | ^0.2 | 0.2.189 | up to date |
| lightproc | ^0.3 | 0.3.5 | up to date |
| num_cpus | ^1.13 | 1.17.0 | up to date |
| once_cell | ^1.4.0 | 1.21.4 | up to date |
| pin-utils | ^0.1.0 | 0.1.0 | up to date |
| tokio ⚠️ | ^1.1 | 1.53.1 | maybe insecure |
| tracing | ^0.1.19 | 0.1.44 | up to date |
| winapi | ^0.3.8 | 0.3.9 | up to date |
(5 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures | ^0.3.5 | 0.3.33 | up to date |
| proptest | ^1.0 | 1.11.0 | up to date |
| tokio ⚠️ | ^1.1 | 1.53.1 | maybe insecure |
| tokio-test | ^0.4.0 | 0.4.5 | up to date |
| tracing-subscriber ⚠️ | ^0.3 | 0.3.23 | maybe insecure |
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);
tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequencesPrevious versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:
In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.
This was patched in PR #3368 to escape ANSI control characters from user input.
crossbeam-epoch: Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalidAffected versions of fmt::Display dereference the underlying pointer. This causes a invalid pointer dereference e.g., when a pointer created with Atomic::null or Shared::null. fmt::Debug impls and pre-0.9 fmt::Display impls, which do not dereference pointers, are not affected by this issue.