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 virtual-fs

Dependencies

(21 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.661.0.98up to date
 async-trait^0.10.1.88up to date
 bytes^11.10.1up to date
 derivative^2.2.02.2.0up to date
 filetime^0.2.180.2.25up to date
 fs_extra^1.2.01.3.0up to date
 futures^0.30.3.31up to date
 getrandom^0.20.3.3out of date
 indexmap^1.9.22.10.0out of date
 lazy_static^1.41.5.0up to date
 libc^0.20.2.174up to date
 pin-project-lite^0.2.90.2.16up to date
 replace_with^0.1.70.1.8up to date
 serde^1.01.0.219up to date
 shared-buffer^0.1.40.1.4up to date
 slab^0.40.4.10up to date
 thiserror^12.0.12out of date
 tokio ⚠️^11.46.1maybe insecure
 tracing^0.10.1.41up to date
 typetag^0.10.2.20out of date
 webc^5.09.0.0out of date

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 pretty_assertions^1.3.01.4.1up to date
 tempfile^3.6.03.20.0up to date
 tokio ⚠️^11.46.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);