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 alloy-transport-ipc

Dependencies

(13 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 alloy-json-rpc^0.60.8.1out of date
 alloy-pubsub^0.60.8.1out of date
 alloy-transport^0.60.8.1out of date
 bytes^1.5.01.9.0up to date
 futures^0.30.3.31up to date
 interprocess^22.2.2up to date
 pin-project^1.11.1.7up to date
 serde^1.01.0.216up to date
 serde_json^1.01.0.133up to date
 tempfile^3.103.14.0up to date
 tokio ⚠️^11.42.0maybe insecure
 tokio-util^0.70.7.13up to date
 tracing^0.10.1.41up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tokio-test^0.40.4.4up 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);