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 topgrade

Dependencies

(23 total, 12 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.4.60.4.41maybe insecure
 console^0.9.00.16.0out of date
 directories^2.0.16.0.0out of date
 failure^0.1.50.1.8up to date
 failure_derive^0.1.50.1.8up to date
 futures^0.1.270.3.31out of date
 glob^0.3.00.3.2up to date
 lazy_static^1.3.01.5.0up to date
 log^0.4.60.4.27up to date
 nix^0.15.00.30.1out of date
 openssl-probe^0.1.20.1.6up to date
 pretty_env_logger^0.3.00.5.0out of date
 rust-ini^0.13.00.21.2out of date
 self_update^0.8.00.42.0out of date
 serde^1.0.921.0.219up to date
 shellexpand^1.0.03.1.1out of date
 structopt^0.3.00.3.26up to date
 strum^0.16.00.27.1out of date
 tokio ⚠️^0.1.211.46.1out of date
 tokio-process^0.2.30.2.5up to date
 toml^0.5.10.8.23out of date
 walkdir^2.2.72.5.0up to date
 which^2.0.18.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

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.