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

Dependencies

(9 total, 1 possibly insecure)

CrateRequiredLatestStatus
 ac-ffmpeg^0.180.18.1up to date
 bytes^11.7.2up to date
 futures^0.30.3.31up to date
 log^0.40.4.22up to date
 rand^0.80.8.5up to date
 socket2^0.50.5.7up to date
 srt-protocol^0.4.40.4.4up to date
 tokio ⚠️^11.40.0maybe insecure
 tokio-stream^0.10.1.16up to date

Dev dependencies

(10 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.89up to date
 assert_matches^1.0.01.5.0up to date
 lazy_static^11.5.0up to date
 libc^0.20.2.159up to date
 libloading^0.80.8.5up to date
 pretty_env_logger^0.50.5.0up to date
 rand^0.80.8.5up to date
 rand_distr^0.40.4.3up to date
 tokio ⚠️^11.40.0maybe insecure
 tokio-util^0.70.7.12up 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);