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-core

Dependencies

(17 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.99up to date
 assert_cfg^0.1.00.1.0up to date
 librqbit-bencode^3.13.1.0up to date
 librqbit-buffers^4.24.2.0up to date
 bytes^1.7.11.10.1up to date
 librqbit-clone-to-owned^33.0.1up to date
 data-encoding^2.6.02.9.0up to date
 directories^66.0.0up to date
 hex^0.40.4.3up to date
 itertools^0.140.14.0up to date
 parking_lot^0.120.12.4up to date
 rand^0.90.9.2up to date
 serde^11.0.219up to date
 tokio ⚠️^11.47.1maybe insecure
 tokio-util^0.7.100.7.16up to date
 tracing^0.1.400.1.41up to date
 url^22.5.7up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 serde_json^11.0.143up 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);