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 s2gpp

Dependencies

(27 total, 12 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix=0.12.00.13.3out of date
 actix-broker^0.4.10.4.3up to date
 actix-telepathy=0.4.10.6.0out of date
 anyhow^1.0.411.0.83up to date
 console^0.15.00.15.8up to date
 csv^1.1.61.3.0up to date
 env_logger^0.9.00.11.3out of date
 futures-sink^0.3.210.3.30up to date
 indexmap^1.82.2.6out of date
 indicatif^0.16.20.17.8out of date
 itertools^0.10.30.12.1out of date
 kdtree^0.6.00.7.0out of date
 log^0.40.4.21up to date
 meanshift-rs^0.8.00.9.3out of date
 ndarray^0.150.15.6up to date
 ndarray-linalg^0.140.16.0out of date
 ndarray-stats^0.50.5.1up to date
 ndarray_einsum_beta^0.7.00.7.0up to date
 num-integer^0.1.440.1.46up to date
 num-traits^0.2.140.2.19up to date
 numpy^0.160.21.0out of date
 pyo3^0.160.21.2out of date
 serde^1.01.0.200up to date
 serde_with^1.9.13.8.1out of date
 sortedvec^0.5.00.5.0up to date
 structopt^0.30.3.26up to date
 tokio ⚠️^1.121.37.0maybe insecure

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 actix-rt^2.2.02.9.0up to date
 port_scanner^0.1.50.1.5up to date
 rayon^1.5.01.10.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);