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

Dependencies

(15 total, 1 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 aws-smithy-async^1.2.11.3.0up to date
 aws-smithy-runtime^1.7.11.14.0up to date
 aws-smithy-runtime-api^1.7.21.16.0up to date
 aws-smithy-types^1.2.41.6.3up to date
 h2 ⚠️^0.40.4.19maybe insecure
 http^11.5.0up to date
 hyper^11.11.1up to date
 hyper-rustls^0.270.27.9up to date
 hyper-util^0.1.70.1.20up to date
 once_cell^1.18.01.21.4up to date
 pin-project-lite^0.2.130.2.17up to date
 rustls ⚠️^0.230.23.44maybe insecure
 tokio ⚠️^11.53.1maybe insecure
 tower^0.4.10.5.3out of date
 tracing^0.1.400.1.44up to date

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 aws-smithy-async^1.2.11.3.0up to date
 aws-smithy-runtime^1.7.11.14.0up to date
 tokio ⚠️^11.53.1maybe insecure

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);

rustls: rustls network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.

h2: h2 unbounded empty DATA frames

RUSTSEC-2026-0258

The h2 crate, used internally by hyper, had a flaw that would accept and queue empty DATA frames without limit. If streams were not actively drained, this could lead to unbounded memory usage, or a panic if the length overflows.

Low severity.

Patched in v0.4.16.