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 igd-next

Dependencies

(15 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^11.13.0up to date
 async-trait^0.1.720.1.83up to date
 attohttpc^0.240.28.0out of date
 bytes^11.8.0up to date
 futures^0.30.3.31up to date
 http^11.1.0up to date
 http-body-util^0.10.1.2up to date
 hyper^11.5.0up to date
 hyper-util^0.10.1.10up to date
 log^0.40.4.22up to date
 rand^0.80.8.5up to date
 surf^2.3.22.3.2up to date
 tokio ⚠️^11.41.1maybe insecure
 url^22.5.3up to date
 xmltree^0.100.11.0out of date

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^11.13.0up to date
 simplelog^0.120.12.2up to date
 tokio ⚠️^11.41.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);