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-http

Dependencies

(15 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aws-smithy-eventstream^0.54.40.60.5out of date
 aws-smithy-types^0.54.41.2.9out of date
 bytes^11.8.0up to date
 bytes-utils^0.10.1.4up to date
 futures-core^0.3.140.3.31up to 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
 once_cell^1.101.20.2up to date
 percent-encoding^2.1.02.3.1up to date
 pin-project-lite^0.2.90.2.15up to date
 pin-utils^0.1.00.1.0up to date
 tokio ⚠️^1.8.41.41.1maybe insecure
 tokio-util^0.70.7.12up to date
 tracing^0.10.1.40up to date

Dev dependencies

(9 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-stream^0.30.3.6up to date
 futures-util^0.30.3.31up to date
 hyper^0.14.121.5.0out of date
 pretty_assertions^1.31.4.1up to date
 proptest^11.5.0up to date
 tempfile^3.2.03.14.0up to date
 tokio ⚠️^1.8.41.41.1maybe insecure
 tokio-stream^0.1.50.1.16up to date
 tracing-test^0.2.10.2.5up 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);