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

Crate ordinary-server-utils

Dependencies

(46 total, 1 outdated, 1 insecure)

CrateRequiredLatestStatus
 ahash^0.8.120.8.12up to date
 anyhow^1.0.1041.0.104up to date
 async-compression^0.4.520.4.52up to date
 axum^0.8.90.8.9up to date
 base64^0.23.10.23.1up to date
 blake2^0.11.00.11.0up to date
 blake3^1.8.71.8.7up to date
 bytes^1.12.21.12.2up to date
 foldhash^0.2.00.2.0up to date
 futures-util^0.3.340.3.34up to date
 hashbrown^0.17.10.17.1up to date
 hickory-resolver^0.26.30.26.3up to date
 http-body-util^0.1.50.1.5up to date
 httparse^1.10.11.10.1up to date
 hyper^1.12.01.12.0up to date
 hyper-util^0.1.210.1.21up to date
 metrics^0.24.60.24.6up to date
 metrics-exporter-prometheus^0.18.30.18.3up to date
 num_threads^0.1.80.1.8up to date
 ordinary-auth^0.13.00.13.0up to date
 ordinary-config^0.13.00.13.0up to date
 ordinary-storage^0.13.00.13.0up to date
 rcgen^0.14.100.14.10up to date
 ref-cast^1.0.271.0.27up to date
 reqwest^0.13.50.13.5up to date
 rustc-hash^2.1.32.1.3up to date
 rustls-acme^0.15.40.15.4up to date
 rustls-platform-verifier^0.7.10.7.1up to date
 scopeguard^1.2.01.2.0up to date
 serde^1.0.2291.0.229up to date
 serde_json^1.0.1541.0.154up to date
 simd-json^0.19.00.19.0up to date
 sysinfo^0.40.40.40.4up to date
 thiserror^2.0.212.0.21up to date
 time^0.3.550.3.55up to date
 tinyvec^1.13.31.13.3up to date
 tokio^1.54.11.54.1up to date
 tokio-rustls^0.26.60.26.6up to date
 tower^0.5.30.5.3up to date
 tower-http^0.7.10.7.1up to date
 tracing^0.1.440.1.44up to date
 url^2.5.82.5.8up to date
 uuid^1.29.31.29.3up to date
 valuable^0.1.10.1.1up to date
 xxhash-rust^0.8.210.8.21up to date
 zstd ⚠️=0.13.30.14.4insecure

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.