Deps.rs

libp2p-quic 0.10.2

[![dependency status](https://deps.rs/crate/libp2p-quic/0.10.2/status.svg)](https://deps.rs/crate/libp2p-quic/0.10.2)

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

Crate libp2p-quic

Dependencies

(17 total, 9 outdated, 1 insecure)

CrateRequiredLatestStatus
 async-std^1.12.01.13.2up to date
 bytes^1.5.01.12.1up to date
 futures^0.3.290.3.34up to date
 futures-timer^3.0.23.0.4up to date
 if-watch^3.2.03.2.2up to date
 libp2p-core^0.41.20.44.0out of date
 libp2p-identity^0.2.80.3.0out of date
 libp2p-tls^0.3.00.7.0out of date
 parking_lot^0.12.00.12.5up to date
 quinn^0.10.20.11.12out of date
 rand^0.8.50.10.3out of date
 ring ⚠️^0.16.200.17.14insecure
 rustls^0.21.90.23.45out of date
 socket2^0.5.50.6.5out of date
 thiserror^1.0.502.0.21out of date
 tokio^1.34.01.53.1up to date
 tracing^0.1.370.1.44up to date

Dev dependencies

(8 total, 4 outdated)

CrateRequiredLatestStatus
 async-std^1.12.01.13.2up to date
 libp2p-identity^0.2.80.3.0out of date
 libp2p-noise^0.44.00.47.0out of date
 libp2p-tcp^0.41.00.45.0out of date
 libp2p-yamux^0.45.10.48.0out of date
 quickcheck^11.1.0up to date
 tokio^1.34.01.53.1up 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.