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.

Crate wasi-tokio

Dependencies

(9 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.221.0.97up to date
 cap-std^1.0.03.4.2out of date
 io-extras^0.17.00.18.4out of date
 io-lifetimes^1.0.02.0.4out of date
 rustix^0.36.71.0.2out of date
 tokio ⚠️^1.8.01.44.1maybe insecure
 wasi-cap-std-sync=8.0.117.0.3out of date
 wasi-common=8.0.130.0.2out of date
 wiggle=8.0.130.0.2out of date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 cap-tempfile^1.0.03.4.2out of date
 tempfile^3.1.03.19.0up to date
 tokio ⚠️^1.8.01.44.1maybe insecure

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On 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.

Workarounds

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);