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.
futures-locks(3 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-channel | ^0.3.1 | 0.3.31 | up to date |
| futures-task ⚠️ | ^0.3.1 | 0.3.31 | maybe insecure |
| tokio ⚠️ | ^1.0 | 1.41.1 | maybe insecure |
(3 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures | ^0.3.1 | 0.3.31 | up to date |
| tokio ⚠️ | ^1.0 | 1.41.1 | maybe insecure |
| tokio-test | ^0.4.2 | 0.4.4 | 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.
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);