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

Crate async-tungstenite

Dependencies

(15 total, 8 outdated, 2 insecure)

CrateRequiredLatestStatus
 async-std^1.01.9.0up to date
 futures-io^0.30.3.13up to date
 futures-util^0.30.3.13insecure
 gio^0.80.9.1out of date
 glib^0.90.10.3out of date
 log^0.40.4.14up to date
 openssl^0.100.10.32insecure
 pin-project^0.41.0.5out of date
 async-native-tls^0.3.00.3.3up to date
 async-tls^0.70.11.0out of date
 native-tls^0.20.2.7up to date
 tokio-native-tls^0.10.3.0out of date
 tokio-openssl^0.40.6.1out of date
 tokio^0.21.2.0out of date
 tungstenite^0.11.00.13.0out of date

Dev dependencies

(4 total, 1 outdated)

CrateRequiredLatestStatus
 async-std^1.01.9.0up to date
 env_logger^0.70.8.3out of date
 futures^0.30.3.13up to date
 url^2.0.02.2.1up to date

Security Vulnerabilities

openssl: Use after free in CMS Signing

RUSTSEC-2018-0010

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

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.