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 tokio-serial

Dependencies

(8 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.10.1up to date
 cfg-if^11.0.0up to date
 futures^0.30.3.31up to date
 log^0.40.4.26up to date
 mio-serial^5.0.35.0.6up to date
 serialport^44.7.0up to date
 tokio ⚠️^1.81.44.1maybe insecure
 tokio-util^0.7.120.7.14up to date

Dev dependencies

(6 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.911.0.97up to date
 bytes^11.10.1up to date
 cpal^0.15.30.15.3up to date
 env_logger^0.10.00.11.7out of date
 tokio ⚠️^1.81.44.1maybe insecure
 tokio-util^0.7.120.7.14up 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);