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-jaeger

Dependencies

(20 total, 8 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.61.12.0up to date
 async-trait^0.10.1.80up to date
 base64^0.130.22.1out of date
 futures-util^0.30.3.30up to date
 headers^0.3.20.4.0out of date
 http^0.21.1.0out of date
 isahc^0.91.7.2out of date
 js-sys^0.30.3.69up to date
 lazy_static^1.41.4.0up to date
 opentelemetry^0.120.22.0out of date
 opentelemetry-http^0.10.11.1out of date
 pin-project^1.01.1.5up to date
 reqwest^0.110.12.4out of date
 surf^2.02.3.2up to date
 thiserror^1.01.0.60up to date
 thrift^0.130.17.0out of date
 tokio ⚠️^1.01.37.0maybe insecure
 wasm-bindgen^0.20.2.92up to date
 wasm-bindgen-futures^0.4.180.4.42up to date
 web-sys^0.3.40.3.69up to date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 futures^0.30.3.30up to date
 opentelemetry^0.120.22.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);