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 tokio-websockets

Dependencies

(22 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 aws-lc-rs^11.12.2up to date
 base64^0.220.22.1up to date
 bytes^1.71.9.0up to date
 fastrand^2.02.3.0up to date
 futures-core^0.30.3.31up to date
 futures-sink^0.30.3.31up to date
 getrandom^0.20.3.1out of date
 http^11.2.0up to date
 httparse^1.61.10.0up to date
 openssl ⚠️^0.100.10.69maybe insecure
 rand^0.80.9.0out of date
 ring^0.170.17.8up to date
 rustls-native-certs^0.80.8.1up to date
 rustls-pki-types^11.11.0up to date
 rustls-platform-verifier^0.3.10.5.0out of date
 sha1_smol^1.01.0.1up to date
 simdutf8^0.10.1.5up to date
 tokio ⚠️^11.43.0maybe insecure
 tokio-native-tls^0.30.3.1up to date
 tokio-rustls^0.260.26.1up to date
 tokio-util^0.7.30.7.13up to date
 webpki-roots^0.260.26.8up to date

Dev dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-util^0.3.140.3.31up to date
 rustls-pemfile^22.2.0up to date
 rustls-pki-types^11.11.0up to date
 tokio ⚠️^11.43.0maybe insecure
 tokio-rustls^0.260.26.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: `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.