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 leptos_reactive

Dependencies

(25 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.220.22.1up to date
 bytecheck^0.70.8.0out of date
 cfg-if^11.0.0up to date
 futures^0.30.3.31up to date
 indexmap^22.6.0up to date
 js-sys^0.30.3.72up to date
 miniserde^0.10.1.40up to date
 oco_ref^0.1.00.2.0out of date
 paste^11.0.15up to date
 pin-project^11.1.7up to date
 rkyv^0.7.390.8.8out of date
 rustc-hash^12.0.0out of date
 self_cell^1.0.01.0.4up to date
 serde^11.0.215up to date
 serde-lite^0.50.5.0up to date
 serde-wasm-bindgen^0.60.6.5up to date
 serde_json^11.0.132up to date
 slotmap^11.0.7up to date
 spin-sdk^33.1.0up to date
 thiserror^12.0.3out of date
 tokio ⚠️^11.41.1maybe insecure
 tracing^0.10.1.40up to date
 wasm-bindgen^0.20.2.95up to date
 wasm-bindgen-futures^0.40.4.45up to date
 web-sys^0.30.3.72up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 log^0.40.4.22up to date
 tokio-test^0.40.4.4up 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);