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

CrateRequiredLatestStatus
 base64^0.13.00.22.1out of date
 bytes^1.1.01.10.1up to date
 chrono ⚠️^0.4.190.4.40maybe insecure
 dirs-next^2.0.02.0.0up to date
 either^1.6.11.15.0up to date
 futures^0.3.170.3.31up to date
 http^0.2.51.3.1out of date
 http-body^0.4.21.0.1out of date
 hyper^0.14.131.6.0out of date
 hyper-openssl^0.9.20.10.2out of date
 hyper-rustls^0.23.00.27.5out of date
 hyper-timeout^0.4.10.5.2out of date
 jsonpath_lib^0.3.00.3.0up to date
 k8s-openapi^0.16.00.24.0out of date
 kube-core=0.76.00.99.0out of date
 openssl ⚠️^0.10.360.10.71maybe insecure
 pem^1.0.13.0.5out of date
 pin-project^1.0.41.1.10up to date
 rand^0.8.30.9.0out of date
 rustls ⚠️^0.20.30.23.23out of date
 rustls-pemfile^1.0.02.2.0out of date
 secrecy^0.8.00.10.3out of date
 serde^1.0.1301.0.219up to date
 serde_json^1.0.681.0.140up to date
 serde_yaml^0.8.210.9.34+deprecatedout of date
 tame-oauth^0.7.00.10.0out of date
 thiserror^1.0.292.0.12out of date
 tokio ⚠️^1.14.01.44.1maybe insecure
 tokio-tungstenite^0.17.10.26.2out of date
 tokio-util^0.7.00.7.14up to date
 tower^0.4.60.5.2out of date
 tower-http^0.3.20.6.2out of date
 tracing^0.1.290.1.41up to date

Dev dependencies

(7 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 k8s-openapi^0.16.00.24.0out of date
 kube<1.0.0, >=0.61.00.99.0up to date
 schemars^0.8.60.8.22up to date
 tempfile^3.1.03.19.0up to date
 tokio ⚠️^1.14.01.44.1maybe insecure
 tokio-test^0.4.00.4.4up to date
 tower-test^0.4.00.4.0up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

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.

openssl: ssl::select_next_proto use after free

RUSTSEC-2025-0004

In openssl versions before 0.10.70, ssl::select_next_proto can return a slice pointing into the server argument's buffer but with a lifetime bound to the client argument. In situations where the server buffer's lifetime is shorter than the client buffer's, this can cause a use after free. This could cause the server to crash or to return arbitrary memory contents to the client.

openssl 0.10.70 fixes the signature of ssl::select_next_proto to properly constrain the output buffer's lifetime to that of both input buffers.

In standard usage of ssl::select_next_proto in the callback passed to SslContextBuilder::set_alpn_select_callback, code is only affected if the server buffer is constructed within the callback. For example:

Not vulnerable - the server buffer has a 'static lifetime:

builder.set_alpn_select_callback(|_, client_protos| {
    ssl::select_next_proto(b"\x02h2", client_protos).ok_or_else(AlpnError::NOACK)
});

Not vulnerable - the server buffer outlives the handshake:

let server_protos = b"\x02h2".to_vec();
builder.set_alpn_select_callback(|_, client_protos| {
    ssl::select_next_proto(&server_protos, client_protos).ok_or_else(AlpnError::NOACK)
});

Vulnerable - the server buffer is freed when the callback returns:

builder.set_alpn_select_callback(|_, client_protos| {
    let server_protos = b"\x02h2".to_vec();
    ssl::select_next_proto(&server_protos, client_protos).ok_or_else(AlpnError::NOACK)
});