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 azure_core

Dependencies

(14 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-lock^3.03.4.1up to date
 async-trait^0.10.1.89up to date
 bytes^1.01.10.1up to date
 futures^0.30.3.31up to date
 hmac^0.120.12.1up to date
 openssl^0.10.720.10.73up to date
 pin-project^1.01.1.10up to date
 serde^1.01.0.225up to date
 serde_json^1.01.0.145up to date
 sha2^0.100.10.9up to date
 tokio ⚠️^1.01.47.1maybe insecure
 tracing^0.1.400.1.41up to date
 typespec^0.5.00.8.0out of date
 typespec_client_core^0.4.00.7.0out of date

Dev dependencies

(5 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 criterion^0.50.7.0out of date
 thiserror^1.02.0.16out of date
 time^0.3.100.3.43up to date
 tokio ⚠️^1.01.47.1maybe insecure
 tracing-subscriber^0.30.3.20up 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);