Deps.rs

tor-netdoc 0.28.0

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

Dependencies

(39 total, 17 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 amplify^44.9.0up to date
 base64ct^1.5.11.8.3up to date
 bitflags^22.11.0up to date
 cipher^0.4.10.5.0out of 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
 hex^0.40.4.3up to date
 hex-literal^0.41.1.0out of date
 humantime^22.3.0up to date
 itertools^0.14.00.14.0up to date
 once_cell^11.21.3up to date
 phf^0.11.10.13.1out of date
 rand^0.80.10.0out of date
 serde^1.0.1031.0.228up to date
 serde_with^3.0.03.16.1up to date
 signature^22.2.0up to date
 smallvec^1.101.15.1up to date
 subtle^22.6.1up to date
 thiserror^22.0.18up to date
 time ⚠️^0.30.3.47maybe insecure
 tinystr^0.8.00.8.2up to date
 tor-basic-utils^0.28.00.39.0out of date
 tor-bytes^0.28.00.39.0out of date
 tor-cell^0.28.00.39.0out of date
 tor-cert^0.28.00.39.0out of date
 tor-checkable^0.28.00.39.0out of date
 tor-error^0.28.00.39.0out of date
 tor-hscrypto^0.28.00.39.0out of date
 tor-linkspec^0.28.00.39.0out of date
 tor-llcrypto^0.28.00.39.0out of date
 tor-protover^0.28.00.39.0out of date
 tor-units^0.28.00.39.0out of date
 visibility^0.1.00.1.1up to date
 visible^0.0.10.0.1up to date
 void^11.0.2up to date
 weak-table^0.3.00.3.2up to date
 zeroize^11.8.2up to date

Dev dependencies

(5 total, 2 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.231.0.102up to date
 hex-literal^0.41.1.0out of date
 itertools^0.14.00.14.0up to date
 serde_json^1.0.501.0.149up to date
 tor-basic-utils^0.28.00.39.0out of 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.