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-upnp-serve

Dependencies

(22 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.861.0.99up to date
 axum^0.80.8.4up to date
 bstr^1.10.01.12.0up to date
 futures^0.3.300.3.31up to date
 gethostname^11.0.2up to date
 http^1.1.01.3.1up to date
 httparse^1.9.41.10.1up to date
 librqbit-core^55.0.0up to date
 librqbit-sha1-wrapper^44.1.0up to date
 librqbit-upnp^11.0.0up to date
 mime_guess^2.0.52.0.5up to date
 network-interface^2.0.02.0.3up to date
 parking_lot^0.12.30.12.4up to date
 quick-xml^0.37.10.38.3out of date
 reqwest^0.12.70.12.23up to date
 serde^11.0.219up to date
 socket2^0.5.70.6.0out of date
 tokio ⚠️^11.47.1maybe insecure
 tokio-util^0.7.110.7.16up to date
 tracing^0.1.400.1.41up to date
 url^22.5.7up to date
 uuid^1.10.01.18.0up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 tower-http^0.6.20.6.6up to date
 tracing-subscriber^0.3.180.3.19up 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);