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

Dependencies

(18 total, 4 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.01.12.0up to date
 futures-io^0.30.3.25up to date
 futures-util^0.30.3.25up to date
 gio^0.140.16.3out of date
 glib^0.140.16.5out of date
 log^0.40.4.17up to date
 openssl ⚠️^0.100.10.43maybe insecure
 pin-project-lite^0.20.2.9up to date
 async-native-tls^0.3.00.4.0out of date
 async-tls^0.110.11.0up to date
 native-tls^0.20.2.11up to date
 tokio-native-tls^0.30.3.0up to date
 tokio-openssl^0.60.6.3up to date
 tokio-rustls^0.230.23.4up to date
 rustls-native-certs^0.60.6.2up to date
 tokio ⚠️^1.01.23.0maybe insecure
 tungstenite^0.16.00.18.0out of date
 webpki-roots^0.220.22.5up to date

Dev dependencies

(5 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.01.12.0up to date
 env_logger^0.90.10.0out of date
 futures^0.30.3.25up to date
 tokio ⚠️^1.01.23.0maybe insecure
 url^2.0.02.3.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.

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

RUSTSEC-2021-0124

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.