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

(19 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.01.13.0up to date
 futures-io^0.30.3.31up to date
 futures-util^0.30.3.31up to date
 gio^0.200.20.6up to date
 glib^0.200.20.6up to date
 log^0.40.4.22up to date
 openssl ⚠️^0.100.10.68maybe insecure
 pin-project-lite^0.20.2.15up to date
 async-native-tls^0.5.00.5.0up to date
 async-tls^0.130.13.0up to date
 native-tls^0.20.2.12up to date
 tokio-native-tls^0.30.3.1up to date
 tokio-openssl^0.60.6.5up to date
 tokio-rustls^0.260.26.0up to date
 rustls-native-certs^0.70.8.0out of date
 rustls-pki-types^1.0.11.10.0up to date
 tokio ⚠️^1.01.41.1maybe insecure
 tungstenite^0.230.24.0out of date
 webpki-roots^0.260.26.6up to date

Dev dependencies

(10 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.01.13.0up to date
 env_logger^0.100.11.5out of date
 futures^0.30.3.31up to date
 futures-channel^0.30.3.31up to date
 http-body-util^0.10.1.2up to date
 hyper^1.01.5.0up to date
 hyper-util^0.10.1.10up to date
 tokio ⚠️^1.01.41.1maybe insecure
 tungstenite^0.230.24.0out of date
 url^2.0.02.5.3up 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: `MemBio::get_buf` has undefined behavior with empty buffers

RUSTSEC-2024-0357

Previously, MemBio::get_buf called slice::from_raw_parts with a null-pointer, which violates the functions invariants, leading to undefined behavior. In debug builds this would produce an assertion failure. This is now fixed.