Deps.rs

masonry_core 0.4.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 masonry_core

Dependencies

(17 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 accesskit^0.21.10.24.0out of date
 anymap3^1.0.11.0.1up to date
 anymore^1.0.01.0.0up to date
 cursor-icon^1.2.01.2.0up to date
 dpi^0.1.20.1.2up to date
 parley^0.6.00.7.0out of date
 smallvec^1.15.11.15.1up to date
 time ⚠️^0.3.440.3.47maybe insecure
 tracing^0.1.410.1.44up to date
 tracing-core^0.1.330.1.36up to date
 tracing-subscriber^0.3.200.3.23up to date
 tracing-tracy^0.11.40.11.4up to date
 tracing_android_trace^0.1.10.1.1up to date
 tree_arena^0.2.00.2.0up to date
 ui-events^0.2.00.3.0out of date
 vello^0.6.00.8.0out of date
 web-time^1.1.01.1.0up to date

Dev dependencies

(5 total, all up-to-date)

CrateRequiredLatestStatus
 assert_matches^1.5.01.5.0up to date
 float-cmp^0.10.00.10.0up to date
 image^0.25.80.25.10up to date
 insta^1.43.21.46.3up to date
 profiling^1.0.171.0.17up 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.