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 hyper-openssl

Dependencies

(11 total, 1 possibly insecure)

CrateRequiredLatestStatus
 http^1.0.01.1.0up to date
 hyper^1.0.11.5.0up to date
 hyper-util^0.10.1.10up to date
 linked_hash_set^0.10.1.4up to date
 once_cell^11.20.2up to date
 openssl ⚠️^0.10.610.10.68maybe insecure
 openssl-sys^0.9.260.9.104up to date
 parking_lot^0.120.12.3up to date
 pin-project^1.1.31.1.7up to date
 tower-layer^0.30.3.3up to date
 tower-service^0.30.3.3up to date

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 hyper^11.5.0up to date
 hyper-util^0.10.1.10up to date
 tokio ⚠️^11.41.1maybe 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.