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 rust-s3

Dependencies

(30 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^11.13.0up to date
 async-trait^0.10.1.87up to date
 attohttpc^0.280.29.1out of date
 aws-creds^0.380.38.0up to date
 aws-region^0.260.27.0out of date
 base64^0.220.22.1up to date
 block_on_proc^0.20.2.0up to date
 bytes^1.21.10.1up to date
 cfg-if^11.0.0up to date
 futures^0.30.3.31up to date
 hex^0.40.4.3up to date
 hmac^0.120.12.1up to date
 http^11.2.0up to date
 log^0.40.4.26up to date
 maybe-async^0.20.2.10up to date
 md5^0.70.7.0up to date
 minidom^0.160.16.0up to date
 percent-encoding^22.3.1up to date
 quick-xml^0.360.37.2out of date
 reqwest^0.120.12.12up to date
 serde^11.0.219up to date
 serde_derive^11.0.219up to date
 serde_json^11.0.140up to date
 sha2^0.100.10.8up to date
 surf^22.3.2up to date
 thiserror^12.0.12out of date
 time^0.3.60.3.39up to date
 tokio ⚠️^11.44.0maybe insecure
 tokio-stream^0.10.1.17up to date
 url^22.5.4up to date

Dev dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.97up to date
 async-std^11.13.0up to date
 env_logger^0.110.11.7up to date
 tokio ⚠️^11.44.0maybe insecure
 uuid^11.15.1up 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);