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 rdbinsight

Dependencies

(46 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.1001.0.102up to date
 arrow^58.1.058.1.0up to date
 async-trait^0.1.890.1.89up to date
 async_async_io^0.2.30.2.3up to date
 axum^0.8.60.8.9up to date
 backon^1.6.01.6.0up to date
 base64^0.22.10.22.1up to date
 bytes^1.11.11.11.1up to date
 clap^4.5.514.6.1up to date
 clap_complete^4.5.604.6.2up to date
 clickhouse^0.14.00.15.0out of date
 crc^3.3.03.4.0up to date
 futures-util^0.3.310.3.32up to date
 hex^0.4.30.4.3up to date
 http^1.3.11.4.0up to date
 hyper-util^0.1.170.1.20up to date
 itertools^0.14.00.14.0up to date
 lz4_flex^0.12.00.13.0out of date
 lzf^1.0.01.0.0up to date
 memchr^2.7.62.8.0up to date
 mimalloc^0.1.480.1.50up to date
 num_cpus^1.17.01.17.0up to date
 num_enum^0.7.50.7.6up to date
 parquet^58.1.058.1.0up to date
 prometheus^0.14.00.14.0up to date
 rand^0.10.00.10.1up to date
 redis^1.0.31.2.0up to date
 redis-protocol^6.0.06.0.0up to date
 reqwest^0.13.20.13.2up to date
 rmp-serde^1.3.01.3.1up to date
 serde^1.0.2281.0.228up to date
 serde_bytes^0.11.190.11.19up to date
 serde_json^1.0.1451.0.149up to date
 serde_with^3.15.13.18.0up to date
 shadow-rs^1.4.01.7.1up to date
 spire_enum^1.0.01.0.0up to date
 thiserror^2.0.172.0.18up to date
 time ⚠️^0.3.440.3.47maybe insecure
 tokio^1.48.01.52.1up to date
 tokio-util^0.7.160.7.18up to date
 tower-service^0.3.30.3.3up to date
 tracing^0.1.410.1.44up to date
 tracing-subscriber^0.3.200.3.23up to date
 typed-builder^0.23.00.23.2up to date
 url^2.5.72.5.8up to date
 wincode^0.4.10.5.3out of date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 tempfile^3.23.03.27.0up to date
 testcontainers^0.27.00.27.3up to date
 tracing-subscriber^0.3.200.3.23up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 shadow-rs^1.4.01.7.1up 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.