Deps.rs

tor-persist 0.28.0

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

Dependencies

(21 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 amplify^44.9.0up to date
 derive-deftly~1.0.01.6.0out of date
 derive_more^2.0.12.1.1up to date
 filetime^0.20.2.27up to date
 fs-mistrust^0.9.00.13.2out of date
 fslock^0.2.00.2.1up to date
 fslock-guard^0.2.10.5.2out of date
 futures^0.3.140.3.32up to date
 itertools^0.14.00.14.0up to date
 oneshot-fused-workaround^0.2.00.5.2out of date
 paste^11.0.15up to date
 sanitize-filename^0.6.00.6.0up to date
 serde^1.0.1031.0.228up to date
 serde_json^1.0.501.0.149up to date
 thiserror^22.0.18up to date
 time ⚠️^0.30.3.47maybe insecure
 tor-async-utils^0.28.00.39.0out of date
 tor-basic-utils^0.28.00.39.0out of date
 tor-error^0.28.00.39.0out of date
 tracing^0.1.360.1.44up to date
 void^11.0.2up to date

Dev dependencies

(7 total, 2 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.231.0.102up to date
 derive-deftly~1.0.01.6.0out of date
 humantime^22.3.0up to date
 itertools^0.14.00.14.0up to date
 tempfile^33.25.0up to date
 test-temp-dir^0.3.00.6.2out 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.