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 libasuran

Dependencies

(36 total, 20 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 aes^0.3.20.8.4out of date
 aes-ctr^0.3.00.99.99out of date
 anyhow^1.0.261.0.82up to date
 async-std^1.4.01.12.0up to date
 async-trait^0.1.220.1.80up to date
 base64^0.11.00.22.0out of date
 bincode^1.2.11.3.3up to date
 blake2b_simd^0.5.101.0.2out of date
 blake3^0.1.01.5.1out of date
 block-modes^0.3.30.9.1out of date
 byteorder^1.3.21.5.0up to date
 chrono ⚠️^0.4.100.4.38maybe insecure
 digest^0.8.10.10.7out of date
 fastcdc^1.0.23.1.0out of date
 flame^0.2.20.2.2up to date
 flamer^0.4.00.5.0out of date
 futures^0.3.10.3.30up to date
 futures-intrusive^0.2.20.5.0out of date
 hmac^0.7.10.12.1out of date
 lazy_static^1.4.01.4.0up to date
 lru ⚠️^0.4.30.12.3out of date
 num_cpus^1.11.11.16.0up to date
 parking_lot^0.10.00.12.2out of date
 petgraph^0.5.00.6.4out of date
 rand^0.7.20.8.5out of date
 rayon^1.3.01.10.0up to date
 rmp-serde^0.14.01.2.0out of date
 rust-argon2^0.6.12.1.0out of date
 serde^1.0.1041.0.198up to date
 serde_bytes^0.11.30.11.14up to date
 sha2^0.8.10.10.8out of date
 tempfile^3.1.03.10.1up to date
 uuid^0.8.11.8.0out of date
 walkdir^2.2.92.5.0up to date
 zeroize^1.1.01.7.0up to date
 zstd^0.5.10.13.1out of date

Dev dependencies

(5 total, 3 outdated)

CrateRequiredLatestStatus
 criterion^0.3.00.5.1out of date
 dir-diff^0.3.20.3.3up to date
 futures-await-test^0.3.00.3.0up to date
 quickcheck^0.9.01.0.3out of date
 quickcheck_macros^0.8.01.0.0out of 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

lru: Use after free in lru crate

RUSTSEC-2021-0130

Lru crate has use after free vulnerability.

Lru crate has two functions for getting an iterator. Both iterators give references to key and value. Calling specific functions, like pop(), will remove and free the value, and but it's still possible to access the reference of value which is already dropped causing use after free.