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, 7 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.01.12.0up to date
 futures-io^0.30.3.28up to date
 futures-util^0.30.3.28up to date
 gio^0.140.18.2out of date
 glib^0.140.18.2out of date
 log^0.40.4.20up to date
 openssl ⚠️^0.100.10.57maybe insecure
 pin-project-lite^0.20.2.13up to date
 async-native-tls^0.3.00.5.0out of date
 async-tls^0.110.12.0out of date
 native-tls^0.20.2.11up to date
 tokio-native-tls^0.30.3.1up to date
 tokio-openssl^0.60.6.3up to date
 tokio-rustls^0.230.24.1out of date
 rustls-native-certs^0.60.6.3up to date
 tokio ⚠️^1.01.32.0maybe insecure
 tungstenite^0.16.00.20.1out of date
 webpki-roots^0.220.25.2out of 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.28up to date
 tokio ⚠️^1.01.32.0maybe insecure
 url^2.0.02.4.1up to date

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.