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 rupnp

Dependencies

(12 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.01.10.1up to date
 futures-core^0.30.3.31up to date
 futures-util^0.30.3.31up to date
 genawaiter^0.990.99.1up to date
 http^1.01.3.1up to date
 http-body-util^0.1.30.1.3up to date
 hyper^1.01.6.0up to date
 hyper-util^0.1.110.1.13up to date
 if-addrs^0.130.13.4up to date
 roxmltree^0.200.20.0up to date
 ssdp-client^2.02.1.0up to date
 tokio ⚠️^1.01.45.1maybe insecure

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.98up to date
 futures^0.30.3.31up to date
 tokio ⚠️^1.01.45.1maybe insecure

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);