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.
kube(29 total, 14 outdated, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| Inflector | ^0.11.4 | 0.11.4 | up to date |
| async-tungstenite | ^0.11.0 | 0.29.1 | out of date |
| base64 | ^0.13.0 | 0.22.1 | out of date |
| bytes | ^1.0.0 | 1.10.1 | up to date |
| chrono ⚠️ | ^0.4.19 | 0.4.41 | maybe insecure |
| dirs-next | ^2.0.0 | 2.0.0 | up to date |
| either | ^1.6.1 | 1.15.0 | up to date |
| futures | ^0.3.8 | 0.3.31 | up to date |
| futures-util | ^0.3.8 | 0.3.31 | up to date |
| http | ^0.2.2 | 1.3.1 | out of date |
| jsonpath_lib | ^0.2.6 | 0.3.0 | out of date |
| k8s-openapi | ^0.10.0 | 0.25.0 | out of date |
| kube-derive | ^0.47.0 | 1.1.0 | out of date |
| log | ^0.4.11 | 0.4.27 | up to date |
| openssl ⚠️ | ^0.10.32 | 0.10.73 | maybe insecure |
| pem | ^0.8.2 | 3.0.5 | out of date |
| reqwest | ^0.11.0 | 0.12.22 | out of date |
| rustls ⚠️ | ^0.19.0 | 0.23.28 | out of date |
| serde | ^1.0.118 | 1.0.219 | up to date |
| serde_json | ^1.0.61 | 1.0.140 | up to date |
| serde_yaml | ^0.8.14 | 0.9.34+deprecated | out of date |
| static_assertions | ^1.1.0 | 1.1.0 | up to date |
| thiserror | ^1.0.23 | 2.0.12 | out of date |
| time | ^0.2.23 | 0.3.41 | out of date |
| tokio ⚠️ | ^1.0.1 | 1.46.1 | maybe insecure |
| tokio-native-tls | ^0.3.0 | 0.3.1 | up to date |
| tokio-rustls | ^0.22.0 | 0.26.2 | out of date |
| tokio-util | ^0.6.0 | 0.7.15 | out of date |
| url | ^2.2.0 | 2.5.4 | up to date |
(4 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| k8s-openapi | ^0.10.0 | 0.25.0 | out of date |
| schemars | ^0.8.0 | 1.0.3 | out of date |
| tempfile | ^3.1.0 | 3.20.0 | up to date |
| tokio ⚠️ | ^1.0.1 | 1.46.1 | maybe insecure |
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
No workarounds are known.
tokio: reject_remote_clients Configuration corruptionOn 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.
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 inputIf 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: Use-After-Free in `Md::fetch` and `Cipher::fetch`When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.
In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).
The maintainers thank quitbug for reporting this vulnerability to us.