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 librqbit-tracker-comms

Dependencies

(21 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.104up to date
 async-stream^0.30.3.6up to date
 backon^1.51.6.0up to date
 librqbit-bencode^9.0.19.0.1up to date
 librqbit-buffers^9.0.19.0.1up to date
 byteorder^11.5.0up to date
 futures^0.30.3.34up to date
 itertools^0.150.15.0up to date
 librqbit-core^9.0.19.0.1up to date
 librqbit-dualstack-sockets^0.70.7.0up to date
 parking_lot^0.120.12.5up to date
 rand^0.100.10.2up to date
 reqwest^0.130.13.4up to date
 serde^11.0.229up to date
 serde_derive^11.0.229up to date
 serde_with^33.22.0up to date
 tokio ⚠️^11.53.1maybe insecure
 tokio-util^0.70.7.19up to date
 tracing^0.10.1.44up to date
 url^22.5.8up to date
 urlencoding^22.1.3up 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);