Deps.rs

prodash 23.1.2

[![dependency status](https://deps.rs/crate/prodash/23.1.2/status.svg)](https://deps.rs/crate/prodash/23.1.2)

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 prodash

Dependencies

(19 total, 9 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-io^1.0.02.6.0out of date
 atty^0.2.140.2.14up to date
 bytesize^1.0.12.3.1out of date
 compound_duration^1.2.02.0.0out of date
 crosstermion^0.10.10.16.0out of date
 ctrlc^3.1.43.5.2up to date
 dashmap^5.1.06.1.0out of date
 futures-core^0.3.40.3.32up to date
 futures-lite^1.5.02.6.1out of date
 human_format^1.0.31.2.1up to date
 humantime^2.0.02.3.0up to date
 log^0.4.80.4.29up to date
 parking_lot^0.12.10.12.5up to date
 signal-hook^0.3.90.4.3out of date
 time ⚠️^0.3.20.3.47maybe insecure
 tui^0.19.00.19.0up to date
 tui-react^0.19.00.24.0out of date
 unicode-segmentation^1.6.01.12.0up to date
 unicode-width^0.1.70.2.2out of date

Dev dependencies

(11 total, 4 outdated)

CrateRequiredLatestStatus
 argh^0.1.30.1.19up to date
 async-executor^1.1.01.14.0up to date
 async-io^1.1.02.6.0out of date
 atty^0.2.140.2.14up to date
 blocking^1.0.01.6.2up to date
 criterion^0.4.00.8.2out of date
 env_logger^0.10.00.11.9out of date
 futures^0.3.50.3.32up to date
 futures-util^0.3.40.3.32up to date
 once_cell^1.4.01.21.4up to date
 rand^0.8.10.10.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.