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 async-datachannel

Dependencies

(7 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.561.0.92up to date
 datachannel^0.7.40.13.1out of date
 futures^0.3.210.3.31up to date
 parking_lot^0.12.00.12.3up to date
 serde^1.0.1361.0.214up to date
 tokio ⚠️^1.17.01.41.0maybe insecure
 tracing^0.1.320.1.40up to date

Dev dependencies

(5 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-tungstenite^0.17.10.28.0out of date
 futures^0.3.210.3.31up to date
 serde_json^1.0.791.0.132up to date
 tokio ⚠️^1.17.01.41.0maybe insecure
 tracing-subscriber^0.3.90.3.18up 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);