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 unc-primitives

Dependencies

(34 total, 20 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 arbitrary^1.2.31.4.2up to date
 base64^0.210.22.1out of date
 borsh^1.0.01.6.1up to date
 bytesize^1.12.3.1out of date
 cfg-if^1.01.0.4up to date
 chrono ⚠️^0.4.190.4.44maybe insecure
 derive_more^0.99.92.1.1out of date
 easy-ext^0.21.0.3out of date
 enum-map^2.1.02.7.3up to date
 hex^0.4.20.4.3up to date
 num-rational^0.3.10.4.2out of date
 once_cell^1.13.11.21.4up to date
 primitive-types^0.100.14.0out of date
 rand^0.8.50.10.0out of date
 rand_chacha^0.3.10.10.0out of date
 reed-solomon-erasure^46.0.0out of date
 serde^1.0.1361.0.228up to date
 serde_json^1.0.681.0.149up to date
 serde_with^3.03.18.0up to date
 serde_yaml^0.90.9.34+deprecatedup to date
 sha3^0.100.10.8up to date
 smart-default^0.60.7.1out of date
 unc-stdx^0.5.10.12.2out of date
 strum^0.240.28.0out of date
 thiserror^1.0.302.0.18out of date
 time ⚠️^0.3.90.3.47maybe insecure
 tracing^0.1.360.1.44up to date
 unc-crypto^0.5.10.12.2out of date
 unc-fmt^0.5.10.12.2out of date
 unc-o11y^0.5.10.12.2out of date
 unc-parameters^0.5.10.12.2out of date
 unc-primitives-core^0.5.10.12.2out of date
 unc-rpc-error-macro^0.5.10.12.2out of date
 unc-vm-runner^0.5.10.12.2out of date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 assert_matches^1.5.01.5.0up to date
 bencher^0.1.50.1.5up to date
 insta^1.34.01.46.3up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

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.