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 tarpc

Dependencies

(16 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.91up to date
 fnv^1.01.0.7up to date
 futures^0.30.3.31up to date
 humantime^2.02.1.0up to date
 opentelemetry^0.17.00.26.0out of date
 pin-project^1.01.1.6up to date
 rand^0.80.8.5up to date
 serde^1.01.0.213up to date
 static_assertions^1.1.01.1.0up to date
 tarpc-plugins^0.120.13.1out of date
 thiserror^1.01.0.65up to date
 tokio ⚠️^11.41.0maybe insecure
 tokio-serde^0.80.9.0out of date
 tokio-util^0.6.90.7.12out of date
 tracing^0.10.1.40up to date
 tracing-opentelemetry^0.17.20.27.0out of date

Dev dependencies

(13 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 assert_matches^1.41.5.0up to date
 bincode^1.31.3.3up to date
 bytes^11.8.0up to date
 flate2^1.01.0.34up to date
 futures-test^0.30.3.31up to date
 opentelemetry^0.17.00.26.0out of date
 opentelemetry-jaeger^0.16.00.22.0out of date
 pin-utils^0.1.0-alpha0.1.0up to date
 serde_bytes^0.110.11.15up to date
 tokio ⚠️^11.41.0maybe insecure
 tokio-serde^0.80.9.0out of date
 tracing-subscriber^0.30.3.18up to date
 trybuild^1.01.0.101up 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);