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 netwatch

Dependencies

(21 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.95up to date
 bytes^1.71.9.0up to date
 derive_more^1.0.01.0.0up to date
 futures-lite^2.32.6.0up to date
 futures-sink^0.3.250.3.31up to date
 futures-util^0.3.250.3.31up to date
 libc^0.2.1390.2.169up to date
 netdev^0.30.00.32.0out of date
 netlink-packet-core^0.7.00.7.0up to date
 netlink-packet-route^0.17.00.21.0out of date
 netlink-sys^0.8.50.8.7up to date
 once_cell^1.18.01.20.2up to date
 rtnetlink^0.13.00.14.1out of date
 serde^11.0.217up to date
 socket2^0.5.30.5.8up to date
 thiserror^12.0.11out of date
 time^0.3.200.3.37up to date
 tokio ⚠️^11.43.0maybe insecure
 tracing^0.10.1.41up to date
 windows^0.510.59.0out of date
 wmi^0.130.14.4out of date

Dev dependencies

(1 total, 1 possibly insecure)

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