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

Dependencies

(37 total, 1 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 base64^0.22.10.22.1up to date
 bytes^1.1.01.9.0up to date
 chrono^0.4.340.4.39up to date
 either^1.6.11.13.0up to date
 form_urlencoded^1.2.01.2.1up to date
 futures^0.3.170.3.31up to date
 home^0.5.40.5.11up to date
 http^1.1.01.2.0up to date
 http-body^1.0.11.0.1up to date
 http-body-util^0.1.20.1.2up to date
 hyper^1.2.01.5.2up to date
 hyper-http-proxy^11.0.0up to date
 hyper-openssl^0.10.20.10.2up to date
 hyper-rustls^0.27.10.27.5up to date
 hyper-socks2^0.9.00.9.1up to date
 hyper-timeout^0.5.10.5.2up to date
 hyper-util^0.1.90.1.10up to date
 jsonpath-rust^0.7.30.7.3up to date
 k8s-openapi^0.23.00.23.0up to date
 kube-core=0.97.00.97.0up to date
 openssl ⚠️^0.10.360.10.68maybe insecure
 pem^3.0.13.0.4up to date
 rand^0.8.30.8.5up to date
 rustls ⚠️^0.23.160.23.20maybe insecure
 rustls-pemfile^2.0.02.2.0up to date
 secrecy^0.10.20.10.3up to date
 serde^1.0.1301.0.216up to date
 serde_json^1.0.681.0.134up to date
 serde_yaml^0.9.190.9.34+deprecatedup to date
 tame-oauth^0.10.00.10.0up to date
 thiserror^2.0.32.0.9up to date
 tokio ⚠️^1.14.01.42.0maybe insecure
 tokio-tungstenite^0.24.00.26.1out of date
 tokio-util^0.7.00.7.13up to date
 tower^0.5.10.5.2up to date
 tower-http^0.6.10.6.2up to date
 tracing^0.1.360.1.41up to date

Dev dependencies

(9 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.3.170.3.31up to date
 hyper^1.2.01.5.2up to date
 k8s-openapi^0.23.00.23.0up to date
 kube<1.0.0, >=0.61.00.97.0up to date
 schemars^0.8.60.8.21up to date
 tempfile^3.1.03.14.0up to date
 tokio ⚠️^1.14.01.42.0maybe insecure
 tokio-test^0.4.00.4.4up to date
 tower-test^0.4.00.4.0up 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.

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.