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 if-watch

Dependencies

(12 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-io^2.0.02.3.4up to date
 core-foundation^0.9.20.10.0out of date
 fnv^1.0.71.0.7up to date
 futures^0.3.190.3.31up to date
 if-addrs^0.10.00.13.3out of date
 ipnet^2.3.12.10.1up to date
 log^0.4.140.4.22up to date
 rtnetlink^0.10.00.14.1out of date
 smol^1.2.52.0.2out of date
 system-configuration^0.5.00.6.1out of date
 tokio ⚠️^1.21.21.40.0maybe insecure
 windows^0.51.00.58.0out of date

Dev dependencies

(3 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.10.00.11.5out of date
 smol^1.2.52.0.2out of date
 tokio ⚠️^1.21.21.40.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);