Deps.rs

mverleg / file_endec

[![dependency status](https://deps.rs/repo/github/mverleg/file_endec/status.svg)](https://deps.rs/repo/github/mverleg/file_endec)

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 file_endec

Dependencies

(18 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 structopt^0.3.260.3.26up to date
 indicatif^0.17.30.17.11up to date
 rpassword^7.2.07.3.1up to date
 secstr^0.5.10.5.1up to date
 zxcvbn^2.2.13.1.0out of date
 twofish^0.7.10.7.1up to date
 aes^0.8.20.8.4up to date
 ring ⚠️^0.16.200.17.14out of date
 argon2rs^0.2.50.2.5up to date
 bcrypt^0.14.00.17.0out of date
 twox-hash^1.6.32.1.0out of date
 semver^1.0.171.0.26up to date
 data-encoding^2.3.32.8.0up to date
 brotli^3.3.47.0.0out of date
 file_shred^1.1.21.2.1up to date
 lazy_static^1.4.01.5.0up to date
 rand^0.8.50.9.0out of date
 number2name^1.1.21.1.2up to date

Dev dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 criterion^0.4.00.5.1out of date
 regex^1.7.31.11.1up to date
 tempfile^3.4.03.19.0up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 indoc^2.0.12.0.6up 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.