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 async_zip

Dependencies

(8 total, 2 possibly insecure)

CrateRequiredLatestStatus
 async-compression^0.4.20.4.17up to date
 chrono ⚠️^0.40.4.38maybe insecure
 crc32fast^11.4.2up to date
 futures-lite^2.1.02.4.0up to date
 pin-project^11.1.7up to date
 thiserror^11.0.66up to date
 tokio ⚠️^11.41.0maybe insecure
 tokio-util^0.70.7.12up to date

Dev dependencies

(11 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix-multipart^0.60.7.2out of date
 actix-web^44.9.0up to date
 anyhow^11.0.92up to date
 derive_more^0.991.0.0out of date
 env_logger^0.11.20.11.5up to date
 futures^0.30.3.31up to date
 sanitize-filename^0.50.5.0up to date
 tokio ⚠️^11.41.0maybe insecure
 tokio-util^0.70.7.12up to date
 uuid^11.11.0up to date
 zip^0.6.32.2.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: 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);