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 sfsu

Dependencies

(38 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.99up to date
 bat^0.250.25.0up to date
 cfg-if^1.01.0.3up to date
 chrono ⚠️^0.40.4.41maybe insecure
 clap^4.54.5.47up to date
 console^0.160.16.0up to date
 crossterm^0.290.29.0up to date
 derive_more^2.02.0.1up to date
 dialoguer^0.110.12.0out of date
 futures^0.30.3.31up to date
 glob^0.3.30.3.3up to date
 hashbrown ⚠️^0.150.16.0out of date
 heck^0.50.5.0up to date
 human-panic^2.02.0.3up to date
 indexmap^2.102.11.0up to date
 itertools^0.140.14.0up to date
 konst^0.40.4.2up to date
 log^0.40.4.28up to date
 open^5.15.3.2up to date
 parking_lot^0.120.12.4up to date
 prodash^30.030.0.1up to date
 quork^0.90.9.1up to date
 rand^0.90.9.2up to date
 ratatui^0.290.29.0up to date
 rayon^1.101.11.0up to date
 regex^1.101.11.2up to date
 semver^1.01.0.26up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.143up to date
 shadow-rs^1.21.3.0up to date
 sprinkles-rs^0.220.22.0up to date
 thiserror^2.0.162.0.16up to date
 tokio^1.471.47.1up to date
 vt3^0.70.7.3up to date
 which^8.08.0.0up to date
 windows^0.610.62.0out of date
 windows-version^0.10.1.5up to date
 winreg^0.550.55.0up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 criterion^0.70.7.0up to date
 url^2.5.42.5.7up to date

Build dependencies

(6 total, all up-to-date)

CrateRequiredLatestStatus
 dotenv^0.150.15.0up to date
 git2^0.200.20.2up to date
 shadow-rs^1.01.3.0up to date
 tokio^1.371.47.1up to date
 toml_edit^0.230.23.4up to date
 winres^0.10.1.12up 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

hashbrown: Borsh serialization of HashMap is non-canonical

RUSTSEC-2024-0402

The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding.

This can result in consensus splits and cause equivalent objects to be considered distinct.

This was patched in 0.15.1.