Deps.rs

tor-dirmgr 0.28.0

[![dependency status](https://deps.rs/crate/tor-dirmgr/0.28.0/status.svg)](https://deps.rs/crate/tor-dirmgr/0.28.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 tor-dirmgr

Dependencies

(45 total, 24 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.540.1.89up to date
 base64ct^1.5.11.8.3up to date
 derive_builder_fork_arti^0.11.20.11.2up to date
 derive_more^2.0.12.1.1up to date
 digest^0.10.00.11.0out of date
 educe^0.4.60.6.0out of date
 event-listener^55.4.1up to date
 fs-mistrust^0.9.00.13.2out of date
 fslock^0.2.00.2.1up to date
 futures^0.3.140.3.32up to date
 hex^0.40.4.3up to date
 humantime^22.3.0up to date
 humantime-serde^1.1.11.1.1up to date
 itertools^0.14.00.14.0up to date
 memmap2^0.9.00.9.10up to date
 once_cell^11.21.3up to date
 oneshot-fused-workaround^0.2.00.5.2out of date
 paste^11.0.15up to date
 postage^0.5.00.5.0up to date
 rand^0.80.10.0out of date
 rusqlite^0.32.10.38.0out of date
 safelog^0.4.20.7.2out of date
 scopeguard^11.2.0up to date
 serde^1.0.1031.0.228up to date
 signature^22.2.0up to date
 strum^0.26.30.27.2out of date
 thiserror^22.0.18up to date
 time ⚠️^0.3.200.3.47maybe insecure
 tor-async-utils^0.28.00.39.0out of date
 tor-basic-utils^0.28.00.39.0out of date
 tor-checkable^0.28.00.39.0out of date
 tor-circmgr^0.28.00.39.0out of date
 tor-config^0.28.00.39.0out of date
 tor-consdiff^0.28.00.39.0out of date
 tor-dirclient^0.28.00.39.0out of date
 tor-error^0.28.00.39.0out of date
 tor-geoip^0.28.00.39.0out of date
 tor-guardmgr^0.28.00.39.0out of date
 tor-llcrypto^0.28.00.39.0out of date
 tor-netdir^0.28.00.39.0out of date
 tor-netdoc^0.28.00.39.0out of date
 tor-persist^0.28.00.39.0out of date
 tor-proto^0.28.00.39.0out of date
 tor-rtcompat^0.28.00.39.0out of date
 tracing^0.1.360.1.44up to date

Dev dependencies

(9 total, 4 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.231.0.102up to date
 filetime^0.20.2.27up to date
 float_eq^1.0.01.0.1up to date
 hex-literal^0.41.1.0out of date
 tempfile^33.25.0up to date
 tor-linkspec^0.28.00.39.0out of date
 tor-rtcompat^0.28.00.39.0out of date
 tor-rtmock^0.28.00.39.0out of date
 tracing-test^0.2.40.2.6up 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.