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.
console-subscriber(17 total, 1 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| console-api | ^0.6.0 | 0.6.0 | up to date |
| crossbeam-channel | ^0.5 | 0.5.12 | up to date |
| crossbeam-utils | ^0.8.7 | 0.8.19 | up to date |
| futures-task ⚠️ | ^0.3 | 0.3.30 | maybe insecure |
| hdrhistogram | ^7.3.0 | 7.5.4 | up to date |
| humantime | ^2.1.0 | 2.1.0 | up to date |
| parking_lot | ^0.12 | 0.12.2 | up to date |
| prost-types | ^0.12.0 | 0.12.4 | up to date |
| serde | ^1 | 1.0.198 | up to date |
| serde_json | ^1 | 1.0.116 | up to date |
| thread_local ⚠️ | ^1.1.3 | 1.1.8 | maybe insecure |
| tokio ⚠️ | ^1.21 | 1.37.0 | maybe insecure |
| tokio-stream | ^0.1 | 0.1.15 | up to date |
| tonic | ^0.10 | 0.11.0 | out of date |
| tracing | ^0.1.26 | 0.1.40 | up to date |
| tracing-core | ^0.1.24 | 0.1.32 | up to date |
| tracing-subscriber | ^0.3.17 | 0.3.18 | up to date |
(3 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures | ^0.3 | 0.3.30 | up to date |
| tokio ⚠️ | ^1.21 | 1.37.0 | maybe insecure |
| tower | ^0.4 | 0.4.13 | up to date |
futures-task: futures_task::waker may cause a use-after-free if used on a type that isn't 'staticAffected 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.
thread_local: Data race in `Iter` and `IterMut`In the affected version of this crate, {Iter, IterMut}::next used a weaker memory ordering when loading values than what was required, exposing a potential data race
when iterating over a ThreadLocal's values.
Crates using Iter::next, or IterMut::next are affected by this issue.
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);