This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate tokio-util

Dependencies

(9 total, 1 insecure)

CrateRequiredLatestStatus
 bytes^1.0.01.0.1up to date
 futures-core^0.3.00.3.13up to date
 futures-io^0.3.00.3.13up to date
 futures-sink^0.3.00.3.13up to date
 futures-util^0.3.00.3.13insecure
 log^0.40.4.14up to date
 pin-project-lite^0.2.00.2.4up to date
 slab^0.4.10.4.2up to date
 tokio^1.0.01.2.0up to date

Dev dependencies

(6 total, all up-to-date)

CrateRequiredLatestStatus
 async-stream^0.3.00.3.0up to date
 futures^0.3.00.3.13up to date
 futures-test^0.3.50.3.13up to date
 tokio^1.0.01.2.0up to date
 tokio-stream^0.10.1.3up to date
 tokio-test^0.4.00.4.0up to date

Security Vulnerabilities

futures-util: MutexGuard::map can cause a data race in safe code

RUSTSEC-2020-0059

Affected versions of the crate had a Send/Sync implementation for MappedMutexGuard that only considered variance on T, while MappedMutexGuard dereferenced to U.

This could of led to data races in safe Rust code when a closure used in MutexGuard::map() returns U that is unrelated to T.

The issue was fixed by fixing Send and Sync implementations, and by adding a PhantomData<&'a mut U> marker to the MappedMutexGuard type to tell the compiler that the guard is over U too.