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 wot-serve

Dependencies

(12 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 wot-td^0.5.00.5.0up to date
 mdns-sd^0.11.00.11.5up to date
 thiserror^1.02.0.3out of date
 if-addrs^0.11.00.13.3out of date
 hostname^0.40.4.0up to date
 axum^0.7.20.7.9up to date
 serde^1.0.1411.0.215up to date
 serde_json^1.0.831.0.133up to date
 uuid^1.1.21.11.0up to date
 datta^0.10.1.1up to date
 tower-http^0.5.00.6.2out of date
 tokio ⚠️^1.20.11.41.1maybe insecure

Dev dependencies

(1 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.20.11.41.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);