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 reqwest-retry

Dependencies

(14 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.01.0.86up to date
 async-trait^0.1.510.1.80up to date
 chrono ⚠️^0.4.190.4.38maybe insecure
 futures^0.3.00.3.30up to date
 getrandom^0.2.00.2.15up to date
 http^1.01.1.0up to date
 hyper^1.01.3.1up to date
 parking_lot^0.11.20.12.2out of date
 reqwest^0.12.00.12.4up to date
 reqwest-middleware^0.3.00.3.1up to date
 retry-policies^0.3.00.4.0out of date
 tokio ⚠️^1.6.01.37.0maybe insecure
 tracing^0.1.260.1.40up to date
 wasm-timer^0.2.50.2.5up to date

Dev dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.3.00.3.30up to date
 paste^1.0.01.0.15up to date
 tokio ⚠️^1.0.01.37.0maybe insecure
 wiremock^0.6.00.6.0up 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);