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 netlink-proto

Dependencies

(7 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.01.8.0up to date
 futures^0.30.3.31up to date
 log^0.4.80.4.22up to date
 netlink-packet-core^0.7.00.7.0up to date
 netlink-sys^0.8.40.8.6up to date
 thiserror^1.0.302.0.3out of date
 tokio ⚠️^1.01.41.1maybe insecure

Dev dependencies

(5 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.9.01.13.0up to date
 env_logger^0.8.20.11.5out of date
 netlink-packet-audit^0.5.00.5.1up to date
 netlink-packet-route^0.18.10.21.0out of date
 tokio ⚠️^1.0.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);