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-native-tls

Dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 native-tls^0.20.2.12up to date
 tokio ⚠️^1.01.41.0maybe insecure

Dev dependencies

(11 total, 4 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 cfg-if^0.11.0.0out of date
 env_logger^0.60.11.5out of date
 futures^0.3.00.3.31up to date
 lazy_static^1.4.01.5.0up to date
 tempfile^3.13.13.0up to date
 tokio ⚠️^1.01.41.0maybe insecure
 tokio-util^0.6.00.7.12out of date
 openssl ⚠️^0.100.10.68maybe insecure
 security-framework^0.23.0.0out of date
 schannel^0.10.1.26up to date
 winapi^0.30.3.9up 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.