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 paas-client

Dependencies

(12 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 paas-api^0.30.3.0up to date
 libpep^0.6.60.6.8up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 rand_core^0.60.9.3out of date
 reqwest^0.12.90.12.15up to date
 clap^4.5.274.5.34up to date
 tokio ⚠️^1.0.01.44.1maybe insecure
 base64^0.22.10.22.1up to date
 async-trait^0.1.860.1.88up to date
 thiserror^2.0.112.0.12up to date
 futures^0.3.310.3.31up to date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 chrono^0.4.390.4.40up to date
 tokio ⚠️^11.44.1maybe insecure
 mockito^0.31.01.7.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);