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 opentelemetry

Dependencies

(17 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.61.13.2up to date
 async-trait^0.10.1.89up to date
 crossbeam-channel^0.50.5.15up to date
 dashmap^4.0.16.1.0out of date
 fnv^1.01.0.7up to date
 futures-channel^0.30.3.32up to date
 futures-executor^0.30.3.32up to date
 futures-util^0.30.3.32up to date
 js-sys^0.30.3.94up to date
 lazy_static^1.41.5.0up to date
 percent-encoding^2.02.3.2up to date
 pin-project^1.0.21.1.11up to date
 rand^0.80.10.0out of date
 serde^1.01.0.228up to date
 thiserror^12.0.18out of date
 tokio ⚠️^1.01.51.1maybe insecure
 tokio-stream^0.10.1.18up to date

Dev dependencies

(3 total, 3 outdated)

CrateRequiredLatestStatus
 bincode^1.23.0.0out of date
 criterion^0.3.10.8.2out of date
 rand_distr^0.4.00.6.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);