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-compression


(12 total, 4 outdated, 2 possibly insecure)

 brotli^ to date
 bytes^ of date
 bzip2 ⚠️^ insecure
 flate2^ to date
 futures-core^ to date
 futures-io^ to date
 zstd^ of date
 memchr^ to date
 pin-project-lite^ to date
 tokio ⚠️^ of date
 xz2^ to date
 zstd-safe^ of date

Dev dependencies

(9 total, 5 outdated, 1 possibly insecure)

 bytes^ of date
 futures^ to date
 futures-test^ to date
 ntest^ of date
 proptest^ to date
 proptest-derive^ of date
 rand^ to date
 tokio ⚠️^ of date
 tokio-util^ of date

Security Vulnerabilities

tokio: Task dropped in wrong thread when aborting `LocalSet` task


When aborting a task with JoinHandle::abort, the future is dropped in the thread calling abort if the task is not currently being executed. This is incorrect for tasks spawned on a LocalSet.

This can easily result in race conditions as many projects use Rc or RefCell in their Tokio tasks for better performance.

See tokio#3929 for more details.

tokio: Data race when sending and receiving after closing a `oneshot` channel


If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.

bzip2: bzip2 Denial of Service (DoS)


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.