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 decrypt-cookies

Dependencies

(15 total, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.99up to date
 binary-cookies^0.30.3.1up to date
 chromium-crypto^0.40.4.1up to date
 chrono ⚠️^0.40.4.41maybe insecure
 const_format^0.20.2.34up to date
 dirs^66.0.0up to date
 rawcopy-rs-next^0.1.30.1.3up to date
 rayon^11.11.0up to date
 reqwest^0.120.12.23up to date
 rust-ini^0.210.21.2up to date
 sea-orm^11.1.14up to date
 serde^11.0.219up to date
 snafu^0.80.8.6up to date
 tokio ⚠️^11.47.1maybe insecure
 tracing^0.10.1.41up to date

Dev dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.99up to date
 reqwest^0.120.12.23up to date
 tokio ⚠️^11.47.1maybe insecure
 tracing^0.10.1.41up to date
 tracing-subscriber^0.30.3.19up 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);