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 rezolus

Dependencies

(27 total, 11 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.571.0.82up to date
 async-trait^0.1.560.1.80up to date
 bcc^0.0.320.0.34out of date
 clap^3.2.14.5.4out of date
 crossbeam^0.8.10.8.4up to date
 ctrlc^3.2.23.4.4up to date
 dashmap^5.3.45.5.3up to date
 json^0.12.40.12.4up to date
 kafka^0.8.00.10.0out of date
 libc^0.2.1260.2.154up to date
 num^0.4.00.4.2up to date
 num-derive^0.3.30.4.2out of date
 num-traits^0.2.150.2.19up to date
 nvml-wrapper^0.7.00.10.0out of date
 regex^1.5.61.10.4up to date
 reqwest^0.11.100.12.4out of date
 serde^1.0.1371.0.200up to date
 serde_derive^1.0.1371.0.200up to date
 strum^0.24.10.26.2out of date
 strum_macros^0.24.10.26.2out of date
 sysconf^0.3.40.3.4up to date
 thiserror^1.0.311.0.59up to date
 tiny_http^0.10.00.12.0out of date
 tokio ⚠️^1.19.21.37.0maybe insecure
 toml^0.5.90.8.12out of date
 uuid^0.8.21.8.0out of date
 walkdir^2.3.22.5.0up 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);