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 agnostic-lite

Dependencies

(14 total, 1 possibly insecure)

CrateRequiredLatestStatus
 async-io^22.6.0up to date
 atomic-time^0.20.2.1up to date
 embassy-executor^0.100.10.0up to date
 embassy-futures^0.10.1.2up to date
 embassy-sync^0.80.8.0up to date
 embassy-time^0.50.5.1up to date
 futures-channel^0.30.3.34up to date
 futures-util^0.30.3.34up to date
 paste^11.0.15up to date
 pin-project^11.1.13up to date
 pin-project-lite^0.20.2.17up to date
 feature-extension-for-smol^0.2.10.2.3up to date
 tokio ⚠️^11.53.1maybe insecure
 feature-extension-for-wasm-bindgen-futures^0.2.10.2.3up to date

Dev dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 critical-section^11.2.0up to date
 embassy-executor^0.100.10.0up to date
 embassy-time^0.50.5.1up to date
 futures^0.30.3.34up to date
 tokio ⚠️^11.53.1maybe insecure
 wasm-bindgen-test^0.30.3.78up 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);