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, 7 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 bytes ⚠️^1.1.01.11.1maybe insecure
 compact_str^0.40.9.0out of date
 const_format^0.2.220.2.35up to date
 derive-where^1.2.71.6.0up to date
 either^1.9.01.15.0up to date
 fastrand^2.0.22.3.0up to date
 hashbrown^0.12.00.16.1out of date
 hashlink^0.8.00.11.0out of date
 ignore-result^0.2.00.2.0up to date
 num_enum^0.5.60.7.5out of date
 rustls ⚠️^0.23.20.23.36maybe insecure
 rustls-pemfile^22.2.0up to date
 static_assertions^1.1.01.1.0up to date
 strum^0.230.27.2out of date
 thiserror^1.0.302.0.18out of date
 tokio ⚠️^1.15.01.49.0maybe insecure
 tokio-rustls^0.26.00.26.4up to date
 tracing^0.1.400.1.44up to date
 uuid^1.4.11.20.0up to date
 webpki-roots^0.26.11.0.6out of date

Dev dependencies

(10 total, 4 outdated)

CrateRequiredLatestStatus
 assert_matches^1.5.01.5.0up to date
 assertor^0.0.20.0.4out of date
 env_logger^0.10.00.11.8out of date
 pretty_assertions^1.1.01.4.1up to date
 rand^0.8.40.10.0out of date
 rcgen^0.12.10.14.7out of date
 serial_test^3.0.03.3.1up to date
 tempfile^3.6.03.24.0up to date
 test-case^33.3.1up to date
 test-log^0.2.150.2.19up 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 network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.

bytes: Integer overflow in `BytesMut::reserve`

RUSTSEC-2026-0007

In the unique reclaim path of BytesMut::reserve, the condition

if v_capacity >= new_cap + offset

uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB.

This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.

PoC

use bytes::*;

fn main() {
    let mut a = BytesMut::from(&b"hello world"[..]);
    let mut b = a.split_off(5);

    // Ensure b becomes the unique owner of the backing storage
    drop(a);

    // Trigger overflow in new_cap + offset inside reserve
    b.reserve(usize::MAX - 6);

    // This call relies on the corrupted cap and may cause UB & HBO
    b.put_u8(b'h');
}

Workarounds

Users of BytesMut::reserve are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.