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 madsim

Dependencies

(24 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.80.8.12up to date
 async-channel^22.3.1up to date
 async-stream^0.30.3.6up to date
 async-task^4.44.7.1up to date
 async-ucx^0.10.1.1up to date
 bincode^12.0.1out of date
 bytes^11.10.1up to date
 downcast-rs^1.22.0.1out of date
 futures-util^0.30.3.31up to date
 lazy_static^1.41.5.0up to date
 libc^0.20.2.174up to date
 madsim-macros^0.20.2.12up to date
 naive-timer^0.20.2.0up to date
 panic-message^0.30.3.0up to date
 rand^0.80.9.1out of date
 rand_xoshiro^0.60.7.0out of date
 rustversion^11.0.21up to date
 serde^11.0.219up to date
 spin^0.9.80.10.0out of date
 tokio ⚠️^11.45.1maybe insecure
 tokio-util^0.70.7.15up to date
 toml^0.80.8.23up to date
 tracing^0.10.1.41up to date
 tracing-subscriber^0.30.3.19up to date

Dev dependencies

(4 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 criterion^0.50.6.0out of date
 getrandom=0.2.130.3.3out of date
 structopt^0.30.3.26up to date
 tokio ⚠️^11.45.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);