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 zookeeper-client

Dependencies

(20 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bytes^1.1.01.6.0up to date
 compact_str^0.40.7.1out of date
 const_format^0.2.220.2.32up to date
 derive-where^1.2.71.2.7up to date
 either^1.9.01.13.0up to date
 fastrand^2.0.22.1.0up to date
 hashbrown^0.12.00.14.5out of date
 hashlink^0.8.00.9.1out of date
 ignore-result^0.2.00.2.0up to date
 num_enum^0.5.60.7.2out of date
 rustls ⚠️^0.23.20.23.10maybe insecure
 rustls-pemfile^22.1.2up to date
 static_assertions^1.1.01.1.0up to date
 strum^0.230.26.3out of date
 thiserror^1.0.301.0.61up to date
 tokio ⚠️^1.15.01.38.0maybe insecure
 tokio-rustls^0.26.00.26.0up to date
 tracing^0.1.400.1.40up to date
 uuid^1.4.11.9.1up to date
 webpki-roots^0.26.10.26.3up to date

Dev dependencies

(10 total, 2 outdated)

CrateRequiredLatestStatus
 assert_matches^1.5.01.5.0up to date
 assertor^0.0.20.0.2up to date
 env_logger^0.10.00.11.3out of date
 pretty_assertions^1.1.01.4.0up to date
 rand^0.8.40.8.5up to date
 rcgen^0.12.10.13.1out of date
 serial_test^3.0.03.1.1up to date
 tempfile^3.6.03.10.1up to date
 test-case^33.3.1up to date
 test-log^0.2.150.2.16up 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);

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.