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 zip

Dependencies

(22 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 aes^0.80.8.4up to date
 arbitrary^1.3.21.4.1up to date
 bzip2 ⚠️^0.4.30.5.0out of date
 chrono ⚠️^0.40.4.39maybe insecure
 constant_time_eq^0.30.3.1up to date
 crc32fast^1.41.4.2up to date
 crossbeam-utils^0.8.200.8.21up to date
 deflate64^0.1.90.1.9up to date
 displaydoc^0.20.2.5up to date
 flate2^1.01.0.35up to date
 hmac^0.120.12.1up to date
 indexmap^22.7.0up to date
 lzma-rs^0.30.3.0up to date
 memchr^2.72.7.4up to date
 pbkdf2^0.120.12.2up to date
 rand^0.80.8.5up to date
 sha1^0.100.10.6up to date
 thiserror^22.0.7up to date
 time^0.3.10.3.37up to date
 zeroize^1.81.8.1up to date
 zopfli^0.80.8.1up to date
 zstd^0.130.13.2up to date

Dev dependencies

(7 total, 1 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.601.0.94up to date
 bencher^0.1.50.1.5up to date
 clap=4.4.184.5.23out of date
 getrandom^0.2.150.2.15up to date
 tempfile^3.83.14.0up to date
 time^0.3.10.3.37up to date
 walkdir^2.52.5.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

bzip2: bzip2 Denial of Service (DoS)

RUSTSEC-2023-0004

Working with specific payloads can cause a Denial of Service (DoS) vector.

Both Decompress and Compress implementations can enter into infinite loops given specific payloads entered that trigger it.

The issue is described in great detail in the bzip2 repository issue.

Thanks to bjrjk for finding and providing the patch for the issue and the maintainer responsibly responding to release a fix quickly.

Users who use the crate with untrusted data should update the bzip2 to 0.4.4.