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(20 total, 5 outdated, 5 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| console-api | ^0.8.1 | 0.9.0 | out of date |
| crossbeam-channel | ^0.5 | 0.5.15 | up to date |
| crossbeam-utils | ^0.8.7 | 0.8.21 | up to date |
| futures-task ⚠️ | ^0.3 | 0.3.31 | maybe insecure |
| hdrhistogram | ^7.3.0 | 7.5.4 | up to date |
| humantime | ^2.1.0 | 2.3.0 | up to date |
| hyper-util | ^0.1.6 | 0.1.19 | up to date |
| parking_lot | ^0.12 | 0.12.5 | up to date |
| prost | ^0.13.1 | 0.14.1 | out of date |
| prost-types | ^0.13.1 | 0.14.1 | out of date |
| serde | ^1 | 1.0.228 | up to date |
| serde_json | ^1 | 1.0.147 | up to date |
| thread_local ⚠️ | ^1.1.3 | 1.1.9 | maybe insecure |
| tokio ⚠️ | ^1.21 | 1.48.0 | maybe insecure |
| tokio-stream | ^0.1 | 0.1.17 | up to date |
| tonic ⚠️ | ^0.12 | 0.14.2 | out of date |
| tonic-web | ^0.12 | 0.14.2 | out of date |
| tracing | ^0.1.26 | 0.1.44 | up to date |
| tracing-core | ^0.1.24 | 0.1.36 | up to date |
| tracing-subscriber ⚠️ | ^0.3.17 | 0.3.22 | maybe insecure |
(5 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures | ^0.3 | 0.3.31 | up to date |
| http | ^1.1 | 1.4.0 | up to date |
| tokio ⚠️ | ^1.21 | 1.48.0 | maybe insecure |
| tower | ^0.4 | 0.5.2 | out of date |
| tower-http | ^0.5 | 0.6.8 | out of 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);
tonic: Remotely exploitable Denial of Service in TonicWhen using tonic::transport::Server there is a remote DoS attack that can cause the server to exit cleanly on accepting a tcp/tls stream. This can be triggered via causing the accept call to error out with errors there were not covered correctly causing the accept loop to exit.
More information can be found here
Upgrading to tonic 0.12.3 and above contains the fix.
A custom accept loop is a possible workaround.
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.