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 n5

Dependencies

(14 total, 4 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 byteorder^11.5.0up to date
 bzip2 ⚠️^0.30.4.4out of date
 flate2^1.0.121.0.28up to date
 fs2^0.40.4.3up to date
 itertools^0.80.12.1out of date
 lz4^1.231.24.0up to date
 ndarray^0.130.15.6out of date
 num-traits^0.20.2.18up to date
 semver^0.91.0.22out of date
 serde^1.01.0.198up to date
 serde_json^1.0.391.0.116up to date
 smallvec ⚠️^1.01.13.2maybe insecure
 walkdir^22.5.0up to date
 xz2^0.10.1.7up to date

Dev dependencies

(9 total, 3 outdated)

CrateRequiredLatestStatus
 bencher^0.1.50.1.5up to date
 doc-comment^0.30.3.3up to date
 futures^0.10.3.30out of date
 futures-cpupool^0.1.80.1.8up to date
 lazy_static^1.41.4.0up to date
 rand^0.70.8.5out of date
 rayon^11.10.0up to date
 tempdir^0.30.3.7up to date
 tiff^0.30.9.1out of date

Security Vulnerabilities

smallvec: Buffer overflow in SmallVec::insert_many

RUSTSEC-2021-0003

A bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.

This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.

The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.

Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.

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.