Deps.rs

object_store 0.12.0

[![dependency status](https://deps.rs/crate/object_store/0.12.0/status.svg)](https://deps.rs/crate/object_store/0.12.0)

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 object_store

Dependencies

(28 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.530.1.88up to date
 base64^0.220.22.1up to date
 bytes^1.01.10.1up to date
 chrono^0.4.340.4.41up to date
 form_urlencoded^1.21.2.1up to date
 futures^0.30.3.31up to date
 http^1.2.01.3.1up to date
 http-body-util^0.10.1.3up to date
 httparse^1.8.01.10.1up to date
 humantime^2.12.2.0up to date
 hyper^1.21.6.0up to date
 itertools^0.14.00.14.0up to date
 md-5^0.10.60.10.6up to date
 parking_lot^0.120.12.3up to date
 percent-encoding^2.12.3.1up to date
 quick-xml^0.37.00.37.5up to date
 rand^0.80.9.1out of date
 reqwest^0.120.12.15up to date
 ring ⚠️^0.170.17.14maybe insecure
 rustls-pemfile^2.02.2.0up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 serde_urlencoded^0.70.7.1up to date
 thiserror^2.0.22.0.12up to date
 tokio^1.29.01.45.0up to date
 tracing^0.10.1.41up to date
 url^2.22.5.4up to date
 walkdir^22.5.0up to date

Dev dependencies

(7 total, 2 outdated)

CrateRequiredLatestStatus
 hyper^1.21.6.0up to date
 hyper-util^0.10.1.12up to date
 nix^0.29.00.30.1out of date
 rand^0.80.9.1out of date
 regex^1.11.11.11.1up to date
 reqwest^0.120.12.15up to date
 tempfile^3.1.03.20.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.