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 yew

Dependencies

(20 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64ct^1.5.01.6.0up to date
 bincode^1.3.31.3.3up to date
 console_error_panic_hook^0.10.1.7up to date
 futures^0.30.3.30up to date
 gloo^0.80.11.0out of date
 html-escape^0.2.90.2.13up to date
 implicit-clone^0.30.4.9out of date
 indexmap^12.2.6out of date
 js-sys^0.30.3.69up to date
 prokio^0.1.00.1.0up to date
 rustversion^11.0.17up to date
 serde^11.0.202up to date
 slab^0.40.4.9up to date
 thiserror^1.01.0.60up to date
 tokio ⚠️^1.191.37.0maybe insecure
 tracing^0.1.360.1.40up to date
 wasm-bindgen^0.20.2.92up to date
 wasm-bindgen-futures^0.40.4.42up to date
 web-sys^0.3.590.3.69up to date
 yew-macro^0.20.00.21.0out of date

Dev dependencies

(6 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 gloo^0.80.11.0out of date
 tokio ⚠️^1.191.37.0maybe insecure
 trybuild^11.0.96up to date
 wasm-bindgen-futures^0.40.4.42up to date
 wasm-bindgen-test^0.30.3.42up to date
 web-sys^0.30.3.69up 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);