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

Crate async-tungstenite


(15 total, 8 outdated, 2 insecure)

 async-std^ to date
 futures-io^ to date
 gio^ of date
 glib^ of date
 log^ to date
 pin-project^ of date
 async-native-tls^ to date
 async-tls^ of date
 native-tls^ to date
 tokio-native-tls^ of date
 tokio-openssl^ of date
 tokio^ of date
 tungstenite^ of date

Dev dependencies

(4 total, 1 outdated)

 async-std^ to date
 env_logger^ of date
 futures^ to date
 url^ to date

Security Vulnerabilities

openssl: Use after free in CMS Signing


Affected versions of the OpenSSL crate used structures after they'd been freed.

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


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.