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

Dependencies

(29 total, 13 outdated, 4 possibly insecure)

CrateRequiredLatestStatus
 Inflector^0.11.40.11.4up to date
 async-tungstenite^0.11.00.25.1out of date
 base64^0.13.00.22.0out of date
 bytes^1.0.01.6.0up to date
 chrono ⚠️^0.4.190.4.38maybe insecure
 dirs-next^2.0.02.0.0up to date
 either^1.6.11.11.0up to date
 futures^0.3.80.3.30up to date
 futures-util^0.3.80.3.30up to date
 http^0.2.21.1.0out of date
 jsonpath_lib^0.2.60.3.0out of date
 k8s-openapi^0.10.00.21.1out of date
 kube-derive^0.47.00.90.0out of date
 log^0.4.110.4.21up to date
 openssl ⚠️^0.10.320.10.64maybe insecure
 pem^0.8.23.0.4out of date
 reqwest^0.11.00.12.4out of date
 rustls ⚠️^0.19.00.23.5out of date
 serde^1.0.1181.0.198up to date
 serde_json^1.0.611.0.116up to date
 serde_yaml^0.8.140.9.34+deprecatedout of date
 static_assertions^1.1.01.1.0up to date
 thiserror^1.0.231.0.58up to date
 time^0.2.230.3.36out of date
 tokio ⚠️^1.0.11.37.0maybe insecure
 tokio-native-tls^0.3.00.3.1up to date
 tokio-rustls^0.22.00.26.0out of date
 tokio-util^0.6.00.7.10out of date
 url^2.2.02.5.0up to date

Dev dependencies

(4 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 k8s-openapi^0.10.00.21.1out of date
 schemars^0.8.00.8.16up to date
 tempfile^3.1.03.10.1up to date
 tokio ⚠️^1.0.11.37.0maybe insecure

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);

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.