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 extcap

Dependencies

(7 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.1.01.10.1up to date
 clap^3.1.04.5.38out of date
 log^0.4.140.4.27up to date
 pcap-file^1.1.12.0.0out of date
 futures^0.3.210.3.31up to date
 tokio ⚠️^1.17.01.45.0maybe insecure
 tokio-util^0.7.00.7.15up to date

Dev dependencies

(8 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ctrlc^3.2.13.4.7up to date
 rand^0.8.50.9.1out of date
 serialport^4.0.14.7.1up to date
 simplelog^0.11.20.12.2out of date
 futures^0.3.210.3.31up to date
 tokio-serial^5.4.15.4.5up to date
 tokio ⚠️^1.17.01.45.0maybe insecure
 tokio-util^0.7.00.7.15up 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);