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

(18 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.101.13.0up to date
 async-trait^0.10.1.83up to date
 futures-channel^0.30.3.31up to date
 futures-executor^0.30.3.31up to date
 futures-util^0.30.3.31up to date
 glob^0.3.10.3.1up to date
 http^1.11.2.0up to date
 once_cell^1.131.20.2up to date
 opentelemetry^0.240.27.1out of date
 opentelemetry-http^0.130.27.0out of date
 percent-encoding^2.02.3.1up to date
 rand^0.80.8.5up to date
 serde^1.01.0.216up to date
 serde_json^1.01.0.133up to date
 thiserror^12.0.7out of date
 tokio ⚠️^11.42.0maybe insecure
 tokio-stream^0.1.10.1.17up to date
 url^2.52.5.4up to date

Dev dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 criterion^0.50.5.1up to date
 pprof^0.130.14.0out of date
 temp-env^0.3.60.3.6up 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);