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 tokio-uring

Dependencies

(7 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.01.7.2up to date
 io-uring^0.5.80.7.0out of date
 libc^0.2.800.2.159up to date
 scoped-tls^1.0.01.0.1up to date
 slab^0.4.20.4.9up to date
 socket2^0.4.40.5.7out of date
 tokio ⚠️^1.21.40.0maybe insecure

Dev dependencies

(6 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 criterion^0.4.00.5.1out of date
 futures^0.3.250.3.31up to date
 iai^0.1.10.1.1up to date
 tempfile^3.2.03.13.0up to date
 tokio ⚠️^1.21.01.40.0maybe insecure
 tokio-test^0.4.20.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);