Deps.rs

kube 0.46.1

[![dependency status](https://deps.rs/crate/kube/0.46.1/status.svg)](https://deps.rs/crate/kube/0.46.1)

This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate kube

Dependencies

(29 total, 16 outdated, 2 insecure)

CrateRequiredLatestStatus
 Inflector^0.11.40.11.4up to date
 async-tungstenite^0.9.30.35.0out of date
 base64^0.12.10.23.1out of date
 bytes^0.5.61.12.1out of date
 chrono^0.4.150.4.45up to date
 dirs-next^2.0.02.0.0up to date
 either^1.6.01.18.0up to date
 futures^0.3.50.3.34up to date
 futures-util^0.3.50.3.34up to date
 http^0.2.11.5.0out of date
 jsonpath_lib^0.2.50.3.0out of date
 k8s-openapi^0.10.00.28.0out of date
 kube-derive^0.46.04.2.0out of date
 log^0.4.110.4.34up to date
 openssl^0.10.300.10.81up to date
 pem^0.8.14.0.0out of date
 native-tls^0.20.2.18up to date
 reqwest^0.10.80.13.5out of date
 rustls ⚠️^0.18.10.23.45insecure
 serde^1.0.1111.0.229up to date
 serde_json^1.0.531.0.151up to date
 serde_yaml^0.8.140.9.34+deprecatedout of date
 static_assertions^1.1.01.1.0up to date
 thiserror^1.0.202.0.21out of date
 time^0.2.160.3.55out of date
 tokio ⚠️^0.2.241.53.1insecure
 tokio-native-tls^0.10.3.1out of date
 tokio-rustls^0.14.10.26.6out of date
 url^2.1.12.5.8up to date

Dev dependencies

(4 total, 3 outdated, 1 insecure)

CrateRequiredLatestStatus
 k8s-openapi^0.10.00.28.0out of date
 schemars^0.8.01.2.2out of date
 tempfile^3.1.03.27.0up to date
 tokio ⚠️^0.2.211.53.1insecure

Security Vulnerabilities

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.

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.