Deps.rs

databento 0.59.0

[![dependency status](https://deps.rs/crate/databento/0.59.0/status.svg)](https://deps.rs/crate/databento/0.59.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 databento

Dependencies

(16 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-compression^0.40.4.43up to date
 bon^33.10.0up to date
 chrono>=0.4.340.4.45up to date
 dbn^0.670.68.0out of date
 futures^0.30.3.34up to date
 hex^0.40.4.3up to date
 reqwest^0.130.13.4up to date
 serde^1.01.0.229up to date
 serde_json^1.01.0.151up to date
 sha2^0.110.11.0up to date
 thiserror^2.02.0.20up to date
 time ⚠️>=0.3.350.3.55maybe insecure
 tokio>=1.471.53.1up to date
 tokio-util^0.70.7.19up to date
 tracing^0.10.1.44up to date
 zstd^0.130.13.3up to date

Dev dependencies

(9 total, all up-to-date)

CrateRequiredLatestStatus
 anyhow^1.0.1041.0.104up to date
 async-compression^0.40.4.43up to date
 chrono>=0.4.340.4.45up to date
 clap^4.6.64.6.6up to date
 rstest^0.26.10.26.1up to date
 tempfile^3.27.03.27.0up to date
 tokio^1.531.53.1up to date
 tracing-subscriber^0.3.230.3.23up to date
 wiremock^0.60.6.5up to date

Security Vulnerabilities

time: Denial of Service via Stack Exhaustion

RUSTSEC-2026-0009

Impact

When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.

Patches

A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.

Workarounds

Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.