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 aws-smithy-client

Dependencies

(18 total, 12 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aws-smithy-async^0.54.41.2.1out of date
 aws-smithy-http^0.54.40.60.11out of date
 aws-smithy-http-tower^0.54.40.60.3out of date
 aws-smithy-protocol-test^0.54.40.63.0out of date
 aws-smithy-types^0.54.41.2.9out of date
 bytes^11.8.0up to date
 fastrand^1.4.02.2.0out of date
 http^0.2.31.1.0out of date
 http-body^0.4.41.0.1out of date
 hyper^0.14.121.5.0out of date
 hyper-rustls^0.23.00.27.3out of date
 hyper-tls^0.5.00.6.0out of date
 lazy_static^11.5.0up to date
 pin-project-lite^0.2.70.2.15up to date
 serde^11.0.215up to date
 tokio ⚠️^1.8.41.41.1maybe insecure
 tower^0.4.60.5.1out of date
 tracing^0.10.1.40up to date

Dev dependencies

(5 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aws-smithy-async^0.54.41.2.1out of date
 serde^11.0.215up to date
 serde_json^11.0.133up to date
 tokio ⚠️^1.8.41.41.1maybe insecure
 tower-test^0.4.00.4.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);