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_sdk

Dependencies

(20 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.61.12.0up to date
 async-trait^0.10.1.80up to date
 crossbeam-channel^0.50.5.13up to date
 futures-channel^0.30.3.30up to date
 futures-executor^0.30.3.30up to date
 futures-util^0.3.170.3.30up to date
 glob^0.3.10.3.1up to date
 http^0.21.1.0out of date
 once_cell^1.101.19.0up to date
 opentelemetry^0.210.23.0out of date
 opentelemetry-http^0.100.12.0out of date
 ordered-float^4.04.2.0up to date
 percent-encoding^2.02.3.1up to date
 rand^0.80.8.5up to date
 serde^1.01.0.203up to date
 serde_json^11.0.117up to date
 thiserror^11.0.61up to date
 tokio ⚠️^1.01.37.0maybe insecure
 tokio-stream^0.1.10.1.15up to date
 url^2.22.5.0up to date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 criterion^0.50.5.1up to date
 indexmap^2.02.2.6up to date
 pprof^0.130.13.0up 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);