Deps.rs

prost-reflect-validate 0.2.9

[![dependency status](https://deps.rs/crate/prost-reflect-validate/0.2.9/status.svg)](https://deps.rs/crate/prost-reflect-validate/0.2.9)

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 prost-reflect-validate

Dependencies

(13 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.861.0.102up to date
 email_address^0.2.90.2.9up to date
 http^1.1.01.4.0up to date
 itertools^0.13.00.14.0out of date
 no_deadlocks^1.3.21.3.2up to date
 once_cell^1.19.01.21.3up to date
 prost^0.14.10.14.3up to date
 prost-reflect^0.16.20.16.3up to date
 prost-types^0.14.10.14.3up to date
 prost-validate^0.2.90.2.9up to date
 prost-validate-types^0.2.90.2.9up to date
 regex^1.10.61.12.3up to date
 time ⚠️^0.3.360.3.47maybe insecure

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 prost-reflect-build^0.16.00.16.0up 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.