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 dump_syms

Dependencies

(23 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.93up to date
 bitflags^22.6.0up to date
 cab^0.60.6.0up to date
 clap^44.5.21up to date
 crossbeam^0.80.8.4up to date
 dirs^55.0.1up to date
 futures^0.30.3.31up to date
 goblin^0.80.9.2out of date
 hashbrown^0.140.15.1out of date
 log^0.40.4.22up to date
 lzma-rs^0.3.00.3.0up to date
 num_cpus^1.131.16.0up to date
 once_cell^1.151.20.2up to date
 regex^1.61.11.1up to date
 reqwest^0.120.12.9up to date
 serde^1.01.0.215up to date
 serde_json^1.01.0.133up to date
 sha2^0.100.10.8up to date
 simplelog^0.120.12.2up to date
 symbolic^1212.12.1up to date
 tokio ⚠️^1.231.41.1maybe insecure
 url^2.22.5.3up to date
 uuid^11.11.0up to date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 fxhash^0.20.2.1up to date
 reqwest^0.120.12.9up to date
 tempfile^33.14.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);