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

Dependencies

(16 total, 10 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.80up to date
 futures-core^0.30.3.30up to date
 grpcio^0.120.13.0out of date
 http^0.21.1.0out of date
 opentelemetry^0.210.23.0out of date
 opentelemetry-http^0.100.12.0out of date
 opentelemetry-proto^0.40.6.0out of date
 opentelemetry-semantic-conventions^0.130.15.0out of date
 opentelemetry_sdk^0.210.23.0out of date
 prost^0.11.00.12.6out of date
 reqwest^0.110.12.4out of date
 serde^1.01.0.203up to date
 surf^2.02.3.2up to date
 thiserror^1.01.0.61up to date
 tokio ⚠️^1.01.37.0maybe insecure
 tonic^0.9.00.11.0out of date

Dev dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-util^0.30.3.30up to date
 time^0.30.3.36up to date
 tokio ⚠️^1.01.37.0maybe insecure
 tokio-stream^0.10.1.15up 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);