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-runtime

Dependencies

(16 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.80.8.11up to date
 backoff^0.4.00.4.0up to date
 derivative^2.1.12.2.0up to date
 futures^0.3.170.3.31up to date
 json-patch^0.2.64.0.0out of date
 k8s-openapi^0.16.00.24.0out of date
 kube-client=0.76.00.99.0out of date
 parking_lot^0.12.00.12.3up to date
 pin-project^1.0.21.1.10up to date
 serde^1.0.1301.0.219up to date
 serde_json^1.0.681.0.140up to date
 smallvec^1.7.01.14.0up to date
 thiserror^1.0.292.0.12out of date
 tokio ⚠️^1.14.01.44.1maybe insecure
 tokio-util^0.7.00.7.14up to date
 tracing^0.1.290.1.41up to date

Dev dependencies

(6 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 k8s-openapi^0.16.00.24.0out of date
 kube<1.0.0, >=0.60.00.99.0up to date
 rand^0.8.00.9.0out of date
 schemars^0.8.60.8.22up to date
 serde_json^1.0.681.0.140up to date
 tokio ⚠️^1.14.01.44.1maybe insecure

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