Deps.rs

hickory-proto 0.24.2

[![dependency status](https://deps.rs/crate/hickory-proto/0.24.2/status.svg)](https://deps.rs/crate/hickory-proto/0.24.2)

This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate hickory-proto

Dependencies

(37 total, 15 outdated, 2 insecure)

CrateRequiredLatestStatus
 async-trait^0.1.430.1.92up to date
 backtrace^0.3.500.3.76up to date
 bytes^11.12.1up to date
 cfg-if^11.0.5up to date
 data-encoding^2.2.02.11.1up to date
 enum-as-inner^0.60.7.0out of date
 futures-channel^0.3.50.3.34up to date
 futures-io^0.3.50.3.34up to date
 futures-util^0.3.50.3.34up to date
 h2 ⚠️^0.3.00.4.20insecure
 h3^0.0.30.0.8out of date
 h3-quinn^0.0.40.0.10out of date
 http^0.21.5.0out of date
 idna^1.01.1.0up to date
 ipnet^2.3.02.12.2up to date
 js-sys^0.3.440.3.106up to date
 native-tls^0.20.2.18up to date
 once_cell^1.18.01.21.4up to date
 openssl^0.10.550.10.81up to date
 quinn^0.100.11.12out of date
 rand^0.80.10.3out of date
 ring ⚠️^0.160.17.14insecure
 rustls^0.21.60.23.46out of date
 rustls-native-certs^0.6.30.8.5out of date
 rustls-pemfile^1.0.02.2.0out of date
 serde^1.01.0.229up to date
 socket2^0.50.6.5out of date
 thiserror^1.0.202.0.21out of date
 tinyvec^1.1.11.13.3up to date
 tokio^1.211.53.3up to date
 tokio-native-tls^0.3.00.3.1up to date
 tokio-openssl^0.6.00.6.5up to date
 tokio-rustls^0.24.00.26.6out of date
 tracing^0.1.300.1.44up to date
 url^2.4.02.5.8up to date
 wasm-bindgen^0.2.580.2.129up to date
 webpki-roots^0.25.01.0.9out of date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 futures-executor^0.3.50.3.34up to date
 openssl^0.10.550.10.81up to date
 tokio^1.211.53.3up to date
 tracing-subscriber^0.30.3.23up 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.

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.