Deps.rs

grin_wallet_impls 1.1.0

[![dependency status](https://deps.rs/crate/grin_wallet_impls/1.1.0/status.svg)](https://deps.rs/crate/grin_wallet_impls/1.1.0)

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

Crate grin_wallet_impls

Dependencies

(18 total, 9 outdated, 1 insecure)

CrateRequiredLatestStatus
 blake2-rfc^0.20.2.18up to date
 chrono^0.4.40.4.45up to date
 failure^0.10.1.8up to date
 failure_derive^0.10.1.8up to date
 futures^0.10.3.34out of date
 grin_wallet_config^1.1.05.4.1out of date
 grin_wallet_libwallet^1.1.05.4.1out of date
 grin_wallet_util^1.1.05.4.1out of date
 log^0.40.4.34up to date
 rand^0.50.10.3out of date
 ring ⚠️^0.130.17.14insecure
 serde^11.0.229up to date
 serde_derive^11.0.229up to date
 serde_json^11.0.151up to date
 tokio=0.1.111.53.1out of date
 tokio-core^0.10.1.18up to date
 tokio-retry^0.10.3.2out of date
 uuid^0.71.26.1out of 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.