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

(16 total, 11 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.83up to date
 bitflags^1.22.5.0out of date
 cap-fs-ext^0.19.03.0.0out of date
 cap-std^0.19.03.0.0out of date
 cap-time-ext^0.19.03.0.0out of date
 fs-set-times^0.11.00.20.1out of date
 io-lifetimes^0.3.02.0.3out of date
 lazy_static^1.41.4.0up to date
 rsix^0.22.40.26.0out of date
 system-interface^0.14.00.27.2out of date
 tokio ⚠️^1.8.01.37.0maybe insecure
 tracing^0.1.190.1.40up to date
 wasi-cap-std-sync^0.30.017.0.3out of date
 wasi-common^0.30.020.0.2out of date
 wiggle^0.30.020.0.2out of date
 winapi^0.30.3.9up to date

Dev dependencies

(4 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.83up to date
 cap-tempfile^0.19.03.0.0out of date
 tempfile^3.1.03.10.1up to date
 tokio ⚠️^1.8.01.37.0maybe 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);