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

Crate ordinary-storage

Dependencies

(21 total, 1 outdated, 1 insecure)

CrateRequiredLatestStatus
 anyhow^1.0.1041.0.104up to date
 arrayvec^0.7.80.7.8up to date
 bytes^1.12.21.12.2up to date
 bytesize^2.7.02.7.0up to date
 chacha20poly1305^0.11.00.11.0up to date
 fexbluffers^0.1.30.1.3up to date
 hashbrown^0.17.10.17.1up to date
 ordinary-config^0.13.00.13.0up to date
 ordinary-types^0.13.00.13.0up to date
 parking_lot^0.13.00.13.0up to date
 quick_cache^0.7.00.7.0up to date
 rustc-hash^2.1.32.1.3up to date
 saferlmdb^0.9.350.9.35up to date
 serde_json^1.0.1541.0.154up to date
 smallvec^1.16.31.16.6up to date
 thiserror^2.0.212.0.21up to date
 tokio^1.54.11.54.1up to date
 tracing^0.1.440.1.44up to date
 uuid^1.29.31.29.3up to date
 valuable^0.1.10.1.1up to date
 zstd ⚠️=0.13.30.14.4insecure

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 ordinary-test-utils^0.13.00.13.0up to date

Security Vulnerabilities

zstd: Data from an abandoned stream leaks into the next stream on a reused context

RUSTSEC-2026-0391

The with_context constructors of the stream encoders and decoders used the borrowed context as it was. When a stream was abandoned on a context, for example an encoder dropped before finish() after an error, whatever it left there was carried into the next stream: the input buffered by the previous encoder (up to 128 KiB, or all of it with zstdmt) became the start of the next frame, and a decoder returned undelivered output of the previous stream.

An application reusing one context for data that must stay separate, such as different users' requests, could disclose one user's plaintext to another. Whoever supplies the data can cause the abandonment with invalid input.

The flaw was corrected by resetting the context's session in with_context.