Deps.rs

aws-sigv4 1.2.9

[![dependency status](https://deps.rs/crate/aws-sigv4/1.2.9/status.svg)](https://deps.rs/crate/aws-sigv4/1.2.9)

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

Dependencies

(20 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aws-credential-types^1.2.11.2.1up to date
 aws-smithy-eventstream^0.60.60.60.8up to date
 aws-smithy-http^0.60.120.62.0out of date
 aws-smithy-runtime-api^1.7.31.7.4up to date
 aws-smithy-types^1.2.131.3.0up to date
 bytes^11.10.1up to date
 crypto-bigint^0.5.40.6.1out of date
 form_urlencoded^1.01.2.1up to date
 hex^0.40.4.3up to date
 hmac^0.120.12.1up to date
 http^0.21.2.0out of date
 once_cell^1.81.21.0up to date
 p256^0.110.13.2out of date
 percent-encoding^2.12.3.1up to date
 ring ⚠️^0.17.50.17.13maybe insecure
 sha2^0.100.10.8up to date
 subtle^2.5.02.6.1up to date
 time^0.3.50.3.39up to date
 tracing^0.10.1.41up to date
 zeroize^11.8.1up to date

Dev dependencies

(13 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aws-credential-types^1.2.11.2.1up to date
 aws-smithy-runtime-api^1.7.31.7.4up to date
 bytes^11.10.1up to date
 criterion^0.50.5.1up to date
 hex-literal^0.4.11.0.0out of date
 httparse^1.81.10.1up to date
 pretty_assertions^1.31.4.1up to date
 proptest^1.21.6.0up to date
 ring ⚠️^0.17.50.17.13maybe insecure
 serde^1.0.1801.0.219up to date
 serde_derive^1.0.1801.0.219up to date
 serde_json^1.0.1041.0.140up to date
 time^0.3.50.3.39up to date

Security Vulnerabilities

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.