Deps.rs

minidump 0.26.1

[![dependency status](https://deps.rs/crate/minidump/0.26.1/status.svg)](https://deps.rs/crate/minidump/0.26.1)

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 minidump

Dependencies

(14 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arbitrary^11.4.2up to date
 debugid^0.8.00.8.0up to date
 encoding_rs^0.80.8.41up to date
 memmap2^0.90.9.11up to date
 minidump-common^0.26.10.27.0out of date
 num-traits^0.20.2.19up to date
 procfs-core^0.170.18.0out of date
 prost^0.130.14.4out of date
 range-map^0.20.2.0up to date
 scroll^0.12.00.13.0out of date
 thiserror^22.0.20up to date
 time ⚠️^0.3.340.3.55maybe insecure
 tracing^0.1.340.1.44up to date
 uuid^1.0.01.26.1up to date

Dev dependencies

(4 total, 1 outdated)

CrateRequiredLatestStatus
 ctor^0.41.0.13out of date
 doc-comment^0.3.30.3.4up to date
 env_logger^0.11.10.11.11up to date
 test-assembler^0.1.60.1.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.