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 portmapper

Dependencies

(23 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.22.10.22.1up to date
 bytes^1.71.10.1up to date
 derive_more^1.0.02.0.1out of date
 futures-lite^2.52.6.0up to date
 futures-util^0.3.250.3.31up to date
 hyper-util^0.1.110.1.13up to date
 igd-next^0.16.10.16.1up to date
 iroh-metrics^0.340.34.0up to date
 libc^0.2.1390.2.172up to date
 nested_enum_utils^0.2.00.2.2up to date
 netwatch^0.5.00.5.0up to date
 num_enum^0.70.7.3up to date
 rand^0.80.9.1out of date
 serde^11.0.219up to date
 smallvec^1.11.11.15.0up to date
 snafu^0.8.50.8.6up to date
 socket2^0.5.30.5.10up to date
 time^0.3.200.3.41up to date
 tokio ⚠️^11.45.1maybe insecure
 tokio-util^0.70.7.15up to date
 tower-layer^0.3.30.3.3up to date
 tracing^0.10.1.41up to date
 url^2.52.5.4up to date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ntest^0.90.9.3up to date
 rand_chacha^0.3.10.9.0out of date
 tokio ⚠️^11.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);