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 esphome-client

Dependencies

(7 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.22.10.22.1up to date
 mdns-sd^0.13.110.15.1out of date
 prost^0.14.10.14.1up to date
 snow^0.9.60.10.0out of date
 thiserror^2.02.0.17up to date
 tokio ⚠️^11.48.0maybe insecure
 tracing^0.1.410.1.41up to date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^11.48.0maybe insecure
 tracing-subscriber^0.30.3.20up to date

Build dependencies

(5 total, all up-to-date)

CrateRequiredLatestStatus
 heck^0.5.00.5.0up to date
 proc-macro2^1.0.951.0.101up to date
 prost-build^0.14.10.14.1up to date
 quote^1.0.401.0.41up to date
 regex^1.11.11.12.2up 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);