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

(33 total, 15 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 base64^0.20.00.22.1out of date
 bytes^1.1.01.6.0up to date
 chrono^0.4.230.4.38up to date
 dirs-next^2.0.02.0.0up to date
 either^1.6.11.12.0up to date
 futures^0.3.170.3.30up to date
 http^0.2.51.1.0out of date
 http-body^0.4.21.0.0out of date
 hyper^0.14.131.3.1out of date
 hyper-openssl^0.9.20.10.2out of date
 hyper-rustls^0.24.00.27.1out of date
 hyper-timeout^0.4.10.5.1out of date
 jsonpath_lib^0.3.00.3.0up to date
 k8s-openapi^0.18.00.22.0out of date
 kube-core=0.82.20.91.0out of date
 openssl ⚠️^0.10.360.10.64maybe insecure
 pem^1.1.03.0.4out of date
 pin-project^1.0.41.1.5up to date
 rand^0.8.30.8.5up to date
 rustls ⚠️^0.21.00.23.7out of date
 rustls-pemfile^1.0.02.1.2out of date
 secrecy^0.8.00.8.0up to date
 serde^1.0.1301.0.202up to date
 serde_json^1.0.681.0.117up to date
 serde_yaml^0.9.190.9.34+deprecatedup to date
 tame-oauth^0.9.10.10.0out of date
 thiserror^1.0.291.0.61up to date
 tokio ⚠️^1.14.01.37.0maybe insecure
 tokio-tungstenite^0.18.00.21.0out of date
 tokio-util^0.7.00.7.11up to date
 tower^0.4.130.4.13up to date
 tower-http^0.4.00.5.2out of date
 tracing^0.1.360.1.40up to date

Dev dependencies

(7 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 k8s-openapi^0.18.00.22.0out of date
 kube<1.0.0, >=0.61.00.91.0up to date
 schemars^0.8.60.8.19up to date
 tempfile^3.1.03.10.1up to date
 tokio ⚠️^1.14.01.37.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: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.

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.