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

(20 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.80.8.12up to date
 async-broadcast^0.7.00.7.2up to date
 async-stream^0.3.50.3.6up to date
 async-trait^0.1.640.1.89up to date
 backon^1.31.6.0up to date
 educe^0.6.00.6.0up to date
 futures^0.3.170.3.31up to date
 hashbrown ⚠️^0.15.00.16.1out of date
 hostname^0.40.4.2up to date
 json-patch^44.1.0up to date
 k8s-openapi^0.24.00.26.1out of date
 kube-client=0.99.02.0.1out of date
 parking_lot^0.12.00.12.5up to date
 pin-project^1.0.41.1.10up to date
 serde^1.0.1301.0.228up to date
 serde_json^1.0.681.0.145up to date
 thiserror^2.0.32.0.17up to date
 tokio ⚠️^1.14.01.48.0maybe insecure
 tokio-util^0.7.00.7.17up to date
 tracing^0.1.360.1.43up to date

Dev dependencies

(8 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 k8s-openapi^0.24.00.26.1out of date
 kube<2.0.0, >=0.98.02.0.1out of date
 rand^0.9.00.9.2up to date
 schemars^0.8.61.1.0out of date
 serde_json^1.0.681.0.145up to date
 serde_yaml^0.9.190.9.34+deprecatedup to date
 tokio ⚠️^1.14.01.48.0maybe insecure
 tracing-subscriber ⚠️^0.3.170.3.22maybe 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);

hashbrown: Borsh serialization of HashMap is non-canonical

RUSTSEC-2024-0402

The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding.

This can result in consensus splits and cause equivalent objects to be considered distinct.

This was patched in 0.15.1.

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.