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 typespec_client_core

Dependencies

(19 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.89up to date
 base64^0.220.22.1up to date
 bytes^1.01.10.1up to date
 dyn-clone^1.01.0.20up to date
 futures^0.30.3.31up to date
 getrandom^0.20.3.3out of date
 pin-project^1.01.1.10up to date
 quick-xml^0.310.38.3out of date
 rand^0.80.9.2out of date
 reqwest^0.120.12.23up to date
 serde^1.01.0.225up to date
 serde_json^1.01.0.145up to date
 time^0.3.100.3.43up 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_macros^0.4.00.7.0out of date
 url^2.22.5.7up to date
 uuid^1.01.18.1up to date

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.01.47.1maybe insecure
 tracing^0.1.400.1.41up to date
 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);