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 tokio-cron-scheduler

Dependencies

(14 total, 2 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.40.4.38maybe insecure
 croner^2.0.52.0.6up to date
 english-to-cron^0.10.1.2up to date
 nats^0.25.00.25.0up to date
 num-derive^0.40.4.2up to date
 num-traits^0.20.2.19up to date
 postgres-native-tls^0.5.00.5.0up to date
 postgres-openssl^0.5.00.5.0up to date
 prost^0.130.13.3up to date
 tokio ⚠️^11.41.1maybe insecure
 tokio-postgres^0.70.7.12up to date
 tracing^0.10.1.40up to date
 tracing-subscriber^0.30.3.18up to date
 uuid^11.11.0up to date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.93up to date
 chrono-tz^0.8.50.10.0out of date
 tokio ⚠️^11.41.1maybe insecure

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);