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 rusty-sidekiq

Dependencies

(21 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.740.1.83up to date
 bb8^0.80.8.6up to date
 chrono ⚠️^0.40.4.38maybe insecure
 convert_case^0.6.00.6.0up to date
 cron_clock^0.8.00.8.0up to date
 gethostname^0.20.5.0out of date
 hex^0.40.4.3up to date
 num_cpus^1.131.16.0up to date
 rand^0.80.8.5up to date
 redis^0.220.27.4out of date
 serde^1.01.0.210up to date
 serde_json^11.0.129up to date
 serial_test^3.1.13.1.1up to date
 sha2^0.10.60.10.8up to date
 simple-process-stats^1.0.01.0.0up to date
 slog-term^2.92.9.1up to date
 thiserror^1.01.0.64up to date
 tokio ⚠️^11.40.0maybe insecure
 tokio-util^0.7.100.7.12up to date
 tracing^0.1.400.1.40up to date
 tracing-subscriber^0.3.170.3.18up 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

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);