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 aegisvault

Dependencies

(15 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aes-gcm^0.100.10.3up to date
 anyhow^1.01.0.97up to date
 data-encoding^2.32.8.0up to date
 hex^0.4.30.4.3up to date
 scrypt^0.110.11.0up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 uuid^1.01.15.1up to date
 rand^0.80.9.0out of date
 ring ⚠️^0.170.17.14maybe insecure
 zeroize^11.8.1up to date
 urlencoding^2.1.32.1.3up to date
 url^2.5.22.5.4up to date
 rpassword^7.3.17.3.1up to date
 clap^44.5.32up 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.