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

(17 total, 7 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.01.12.0up to date
 futures-io^0.30.3.30up to date
 futures-util^0.30.3.30up to date
 gio^0.90.19.4out of date
 glib^0.100.19.4out of date
 log^0.40.4.21up to date
 openssl ⚠️^0.100.10.64maybe insecure
 pin-project-lite^0.20.2.14up to date
 async-native-tls^0.3.00.5.0out of date
 async-tls^0.110.13.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.4up to date
 tokio-rustls^0.220.26.0out of date
 tokio ⚠️^1.01.37.0maybe insecure
 tungstenite ⚠️^0.13.00.21.0out of date
 webpki-roots^0.210.26.1out of date

Dev dependencies

(5 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.01.12.0up to date
 env_logger^0.80.11.3out of date
 futures^0.30.3.30up to date
 tokio ⚠️^1.01.37.0maybe insecure
 url^2.0.02.5.0up 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.

tungstenite: Tungstenite allows remote attackers to cause a denial of service

RUSTSEC-2023-0065

The Tungstenite crate through 0.20.0 for Rust allows remote attackers to cause a denial of service (minutes of CPU consumption) via an excessive length of an HTTP header in a client handshake. The length affects both how many times a parse is attempted (e.g., thousands of times) and the average amount of data for each parse attempt (e.g., millions of bytes).