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 lspower

Dependencies

(18 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.82up to date
 async-codec-lite^0.0.00.0.2out of date
 async-trait^0.10.1.80up to date
 auto_impl^0.41.2.0out of date
 bytes^1.01.6.0up to date
 dashmap^4.05.5.3out of date
 futures^0.30.3.30up to date
 httparse^1.3.51.8.0up to date
 log^0.40.4.21up to date
 lsp-types^0.880.95.1out of date
 lspower-macros^0.20.2.1up to date
 serde^1.01.0.198up to date
 serde_json^1.01.0.116up to date
 thiserror^1.01.0.58up to date
 tokio ⚠️^1.31.37.0maybe insecure
 tokio-util^0.60.7.10out of date
 tower-service^0.30.3.2up to date
 twoway^0.2.10.2.2up to date

Dev dependencies

(6 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-tungstenite^0.130.25.1out of date
 env_logger^0.80.11.3out of date
 serde_json^1.01.0.116up to date
 tokio ⚠️^1.31.37.0maybe insecure
 tower-test^0.40.4.0up to date
 ws_stream_tungstenite^0.60.13.0out of 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);