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 opentls

Dependencies

(7 total, 2 possibly insecure)

CrateRequiredLatestStatus
 futures-util^0.3.10.3.30up to date
 log^0.4.50.4.22up to date
 openssl ⚠️^0.10.290.10.66maybe insecure
 openssl-probe^0.10.1.5up to date
 openssl-sys^0.9.550.9.103up to date
 tokio ⚠️^1.0.11.40.0maybe insecure
 url^2.1.12.5.2up to date

Dev dependencies

(6 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.6.01.13.0up to date
 cfg-if^0.1.101.0.0out of date
 env_logger^0.7.10.11.5out of date
 futures^0.3.10.3.30up to date
 hex^0.4.20.4.3up to date
 tokio ⚠️^1.0.11.40.0maybe insecure

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.