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 allocative

Dependencies

(21 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 allocative_derive=0.3.30.3.3up to date
 anyhow^1.0.651.0.98up to date
 bumpalo^3.11.13.19.0up to date
 compact_str^0.80.9.0out of date
 ctor^0.1.260.4.2out of date
 dashmap^5.5.36.1.0out of date
 either^1.81.15.0up to date
 futures^0.3.240.3.31up to date
 hashbrown^0.14.30.15.4out of date
 indexmap^2.2.62.10.0up to date
 num-bigint^0.4.30.4.6up to date
 once_cell^1.15.01.21.3up to date
 parking_lot^0.11.20.12.4out of date
 prost-types^0.11.20.14.1out of date
 relative-path^1.7.02.0.1out of date
 serde_json^1.0.481.0.140up to date
 slab^0.4.70.4.10up to date
 smallvec^1.10.01.15.1up to date
 sorted_vector_map^0.20.2.0up to date
 tokio ⚠️^1.51.46.1maybe insecure
 triomphe^0.1.80.1.14up to date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 inferno^0.11.110.12.3out 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);