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

(24 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 atomic-waker^1.1.21.1.2up to date
 bytes^1.71.10.1up to date
 derive_more^1.0.02.0.1out of date
 js-sys^0.30.3.77up to date
 libc^0.2.1390.2.172up to date
 n0-future^0.1.30.1.3up to date
 nested_enum_utils^0.2.00.2.2up to date
 netdev^0.31.00.35.1out of date
 netlink-packet-core^0.7.00.7.0up to date
 netlink-packet-route^0.23.00.24.0out of date
 netlink-proto^0.11.50.11.5up to date
 netlink-sys^0.8.70.8.7up to date
 iroh-quinn-udp^0.5.50.5.7up to date
 serde^11.0.219up to date
 snafu^0.8.50.8.6up to date
 socket2^0.5.30.5.10up to date
 time^0.3.200.3.41up to date
 tokio ⚠️^11.45.1maybe insecure
 tokio-util^0.70.7.15up to date
 tracing^0.10.1.41up to date
 web-sys^0.3.700.3.77up to date
 windows^0.590.61.1out of date
 windows-result^0.30.3.4up to date
 wmi^0.140.17.2out of date

Dev dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 testresult^0.4.10.4.1up to date
 tokio ⚠️^11.45.1maybe insecure
 tracing-subscriber^0.30.3.19up to date
 tracing-subscriber-wasm^0.1.00.1.0up to date
 wasm-bindgen-test^0.30.3.50up to date

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);