Deps.rs

EmbarkStudios / cargo-deny

[![dependency status](https://deps.rs/repo/github/EmbarkStudios/cargo-deny/status.svg)](https://deps.rs/repo/github/EmbarkStudios/cargo-deny)

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 cargo-deny

Dependencies

(35 total, 1 possibly insecure)

CrateRequiredLatestStatus
 nu-ansi-term^0.500.50.1up to date
 anyhow^1.01.0.97up to date
 askalono^0.50.5.0up to date
 bitvec^1.01.0.1up to date
 camino^1.11.1.9up to date
 cfg-expr^0.180.18.0up to date
 clap^4.54.5.32up to date
 codespan^0.110.11.1up to date
 codespan-reporting^0.110.11.1up to date
 crossbeam^0.80.8.4up to date
 fern^0.70.7.1up to date
 globset^0.40.4.16up to date
 goblin^0.90.9.3up to date
 home^0.50.5.11up to date
 krates^0.180.18.1up to date
 log^0.40.4.26up to date
 memchr^2.72.7.4up to date
 parking_lot^0.120.12.3up to date
 rayon^1.41.10.0up to date
 reqwest^0.120.12.12up to date
 ring ⚠️^0.170.17.13maybe insecure
 rustsec^0.300.30.2up to date
 semver^1.01.0.26up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 smallvec^1.141.14.0up to date
 spdx^0.100.10.8up to date
 strum^0.270.27.1up to date
 tame-index^0.180.18.1up to date
 time^0.30.3.39up to date
 toml-span^0.40.4.1up to date
 twox-hash^2.02.1.0up to date
 url^2.52.5.4up to date
 walkdir^2.32.5.0up to date
 gix^0.700.70.0up to date

Dev dependencies

(6 total, all up-to-date)

CrateRequiredLatestStatus
 fs_extra^1.31.3.0up to date
 insta^1.421.42.2up to date
 tame-index^0.180.18.1up to date
 time^0.30.3.39up to date
 toml-span^0.40.4.1up to date
 tempfile^3.173.18.0up 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.