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 async-zeroconf

Dependencies

(6 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bonjour-sys^0.1.00.3.1out of date
 futures^0.3.160.3.31up to date
 futures-core^0.3.160.3.31up to date
 libc^0.2.980.2.172up to date
 log^0.4.140.4.27up to date
 tokio ⚠️^1.8.11.45.1maybe insecure

Dev dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 doc-comment^0.3.30.3.3up to date
 tokio ⚠️^1.8.11.45.1maybe insecure
 tokio-stream^0.10.1.17up to date
 tokio-test^0.4.20.4.4up 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);