Deps.rs

michaelb / sniprun

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

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 sniprun

Dependencies

(23 total, 14 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 neovim-lib^0.6.10.6.1up to date
 log^0.4.180.4.28up to date
 log-panics^2.1.02.1.0up to date
 simple-logging^2.0.22.0.2up to date
 close_fds^0.3.20.3.2up to date
 thiserror^1.0.692.0.17out of date
 dirs^5.0.16.0.0out of date
 regex^1.11.11.12.2up to date
 strip-ansi-escapes^0.2.00.2.1up to date
 libc^0.2.790.2.177up to date
 serial_test^2.0.03.2.0out of date
 rmp=0.8.80.8.14out of date
 unindent^0.2.30.2.4up to date
 ureq=2.9.03.1.2out of date
 http-rest-file=0.5.00.5.1out of date
 url=2.4.02.5.7out of date
 flate2=1.0.221.1.5out of date
 backtrace=0.3.710.3.76out of date
 ring ⚠️=0.17.110.17.14out of date
 serde_bytes=0.11.150.11.19out of date
 parking_lot=0.12.40.12.5out of date
 parking_lot_core=0.9.110.9.12out of date
 lock_api=0.4.130.4.14out 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.