Vulnerabilities

RUSTSEC-2025-0009

Some AES functions may panic when overflow checking is enabled.

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.

Warnings

RUSTSEC-2025-0012

backoff is unmainted.

The backoff crate is no longer actively maintained. For exponential backoffs/retrying, you can use the backon crate.

RUSTSEC-2024-0384

instant is unmaintained

This crate is no longer maintained, and the author recommends using the maintained web-time crate instead.

RUSTSEC-2024-0436

paste - no longer maintained

The creator of the crate paste has stated in the README.md
that this project is not longer maintained as well as archived the repository