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, 8 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.100up to date
 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
 futures-lite^2.52.6.1up to date
 futures-sink^0.30.3.31up to date
 futures-util^0.30.3.31up to date
 libc^0.2.1390.2.177up to date
 netdev^0.31.00.38.2out of date
 netlink-packet-core^0.7.00.8.1out of date
 netlink-packet-route^0.190.25.1out of date
 netlink-sys^0.8.60.8.7up to date
 once_cell^1.18.01.21.3up to date
 iroh-quinn-udp^0.5.50.5.7up to date
 rtnetlink=0.14.10.18.1out of date
 serde^11.0.228up to date
 socket2^0.5.30.6.1out of date
 thiserror^22.0.17up to date
 time^0.3.200.3.44up to date
 tokio ⚠️^11.48.0maybe insecure
 tokio-util^0.70.7.16up to date
 tracing^0.10.1.41up to date
 windows^0.580.62.2out of date
 wmi^0.140.17.3out of date

Dev dependencies

(1 total, 1 possibly insecure)

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