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 mqtt-protocol

Dependencies

(6 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 byteorder^1.31.5.0up to date
 log^0.40.4.21up to date
 tokio ⚠️^11.38.0maybe insecure
 tokio-util^0.60.7.11out of date
 bytes^1.01.6.0up to date
 thiserror^1.01.0.61up to date

Dev dependencies

(5 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 clap^24.5.7out of date
 env_logger^0.80.11.3out of date
 tokio ⚠️^1.01.38.0maybe insecure
 futures^0.30.3.30up to date
 uuid^0.81.8.0out of 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);