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 mediavault-core

Dependencies

(10 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 serde^11.0.228up to date
 toml^0.81.1.2+spec-1.1.0out of date
 chrono ⚠️^0.40.4.44maybe insecure
 walkdir^22.5.0up to date
 ureq^23.3.0out of date
 serde_json^11.0.149up to date
 natord^11.0.9up to date
 urlencoding^22.1.3up to date
 dirs-next^22.0.0up to date
 matroska^0.300.30.0up to date

Crate mediavault-gui

Dependencies

(7 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 eframe^0.270.34.1out of date
 egui^0.270.34.1out of date
 image^0.250.25.10up to date
 crossbeam-channel^0.50.5.15up to date
 chrono ⚠️^0.40.4.44maybe insecure
 serde^11.0.228up to date
 rfd^0.140.17.2out of date

Crate mediavault-cli

Dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 clap^44.6.0up to date
 chrono ⚠️^0.40.4.44maybe insecure
 serde_json^11.0.149up to date

Crate mediavault-tui

Dependencies

(4 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ratatui^0.290.30.0out of date
 crossterm^0.280.29.0out of date
 chrono ⚠️^0.40.4.44maybe insecure
 anyhow^1.0.1021.0.102up 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