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

Crate tokio-tungstenite

Dependencies

(7 total, 1 outdated, 1 insecure)

CrateRequiredLatestStatus
 futures-util^0.30.3.13insecure
 log^0.40.4.14up to date
 native-tls^0.2.00.2.7up to date
 pin-project^1.01.0.5up to date
 tokio^1.0.01.2.0up to date
 tokio-native-tls^0.3.00.3.0up to date
 tungstenite^0.12.00.13.0out of date

Dev dependencies

(4 total, 1 outdated)

CrateRequiredLatestStatus
 env_logger^0.70.8.3out of date
 futures-channel^0.30.3.13up to date
 tokio^1.0.01.2.0up to date
 url^2.0.02.2.1up 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.