Deps.rs

specta 1.0.5

[![dependency status](https://deps.rs/crate/specta/1.0.5/status.svg)](https://deps.rs/crate/specta/1.0.5)

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 specta

Dependencies

(26 total, 13 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bigdecimal^0.3.00.4.10out of date
 bit-vec^0.6.30.8.0out of date
 bson^2.4.03.1.0out of date
 bytesize^1.1.02.3.1out of date
 chrono^0.4.230.4.44up to date
 ctor^0.1.260.6.3out of date
 document-features^0.2.60.2.12up to date
 glam^0.220.32.0out of date
 indexmap^1.9.12.13.0out of date
 indoc^1.0.82.0.7out of date
 ipnetwork^0.20.00.21.1out of date
 mac_address^1.1.41.1.8up to date
 once_cell^1.16.01.21.3up to date
 openapiv3^1.0.12.2.0out of date
 paste^1.0.91.0.15up to date
 rust_decimal^1.26.11.40.0up to date
 serde^1.0.1471.0.228up to date
 serde_json^1.0.871.0.149up to date
 specta-macros^1.0.51.0.5up to date
 tauri^1.2.12.10.2out of date
 thiserror^1.0.382.0.18out of date
 time ⚠️^0.3.170.3.47maybe insecure
 tokio^1.251.49.0up to date
 uhlc^0.5.10.9.0out of date
 url^2.3.12.5.8up to date
 uuid^1.2.11.21.0up to date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 doc-comment^0.3.30.3.4up to date
 serde^1.0.1471.0.228up to date
 trybuild^1.0.771.0.116up 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.