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

Dependencies

(22 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 aws-credential-types^1.2.11.2.1up to date
 aws-runtime^1.5.11.5.5up to date
 aws-sdk-sso^1.51.01.61.0up to date
 aws-sdk-ssooidc^1.52.01.62.0up to date
 aws-sdk-sts^1.52.01.62.0up to date
 aws-smithy-async^1.2.21.2.5up to date
 aws-smithy-http^0.60.110.62.0out of date
 aws-smithy-json^0.61.10.61.3up to date
 aws-smithy-runtime^1.7.51.8.0up to date
 aws-smithy-runtime-api^1.7.31.7.4up to date
 aws-smithy-types^1.2.101.3.0up to date
 aws-types^1.3.31.3.5up to date
 bytes^1.1.01.10.1up to date
 fastrand^2.0.02.3.0up to date
 hex^0.4.30.4.3up to date
 http^0.2.41.2.0out of date
 ring ⚠️^0.17.50.17.13maybe insecure
 time^0.3.40.3.39up to date
 tokio ⚠️^1.13.11.44.0maybe insecure
 tracing^0.10.1.41up to date
 url^2.3.12.5.4up to date
 zeroize^11.8.1up to date

Dev dependencies

(10 total, 1 outdated)

CrateRequiredLatestStatus
 aws-smithy-async^1.2.21.2.5up to date
 aws-smithy-runtime^1.7.51.8.0up to date
 aws-smithy-runtime-api^1.7.31.7.4up to date
 futures-util^0.3.290.3.31up to date
 hyper-rustls^0.240.27.5out of date
 serde^11.0.219up to date
 serde_json^11.0.140up to date
 tokio^1.23.11.44.0up to date
 tracing-subscriber^0.3.160.3.19up to date
 tracing-test^0.2.40.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);

ring: Some AES functions may panic when overflow checking is enabled.

RUSTSEC-2025-0009

ring::aead::quic::HeaderProtectionKey::new_mask() may panic when overflow checking is enabled. In the QUIC protocol, an attacker can induce this panic by sending a specially-crafted packet. Even unintentionally it is likely to occur in 1 out of every 2**32 packets sent and/or received.

On 64-bit targets operations using ring::aead::{AES_128_GCM, AES_256_GCM} may panic when overflow checking is enabled, when encrypting/decrypting approximately 68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols like TLS and SSH are not affected by this because those protocols break large amounts of data into small chunks. Similarly, most applications will not attempt to encrypt/decrypt 64GB of data in one chunk.

Overflow checking is not enabled in release mode by default, but RUSTFLAGS="-C overflow-checks" or overflow-checks = true in the Cargo.toml profile can override this. Overflow checking is usually enabled by default in debug mode.