Deps.rs

firestore-db-and-auth 0.5.0

[![dependency status](https://deps.rs/crate/firestore-db-and-auth/0.5.0/status.svg)](https://deps.rs/crate/firestore-db-and-auth/0.5.0)

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

Crate firestore-db-and-auth

Dependencies

(9 total, 5 outdated, 1 insecure)

CrateRequiredLatestStatus
 base64^0.10.10.23.1out of date
 biscuit^0.30.8.0out of date
 chrono^0.40.4.45up to date
 reqwest^0.90.13.5out of date
 ring ⚠️^0.160.17.14insecure
 rocket^0.40.5.1out of date
 serde^1.01.0.229up to date
 serde_derive^1.01.0.229up to date
 serde_json^1.01.0.151up 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.