Deps.rs

CodedNil / wallpapy

[![dependency status](https://deps.rs/repo/github/CodedNil/wallpapy/status.svg)](https://deps.rs/repo/github/CodedNil/wallpapy)

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 wallpapy

Dependencies

(18 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 dioxus^0.7.90.7.10up to date
 tracing^0.1.440.1.44up to date
 anyhow^1.0.1031.0.104up to date
 serde^1.0.2281.0.229up to date
 uuid^1.23.41.24.0up to date
 chrono^0.4.450.4.45up to date
 time ⚠️=0.3.360.3.55out of date
 strum^0.28.00.28.0up to date
 gloo-timers=0.3.00.4.0out of date
 sqlx^0.9.00.9.0up to date
 dotenvy^0.15.70.15.7up to date
 serde_json^1.0.1501.0.151up to date
 reqwest=0.12.280.13.4out of date
 tokio^1.52.31.53.1up to date
 axum^0.8.90.8.9up to date
 tower-http^0.7.00.7.0up to date
 image^0.25.100.25.10up to date
 base64^0.22.10.23.1out 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.