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

(14 total, 7 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 base64^0.9.30.22.0out of date
 dirs^1.0.45.0.1out of date
 either^1.5.21.11.0up to date
 failure^0.1.20.1.8up to date
 http ⚠️^0.1.171.1.0out of date
 k8s-openapi^0.4.00.21.1out of date
 log^0.4.60.4.21up to date
 openssl ⚠️^0.10.120.10.64maybe insecure
 reqwest^0.9.170.12.4out of date
 serde^1.0.901.0.198up to date
 serde_derive^1.0.901.0.198up to date
 serde_json^1.0.391.0.116up to date
 serde_yaml^0.8.80.9.34+deprecatedout of date
 url^1.7.22.5.0out of date

Dev dependencies

(3 total, 2 outdated)

CrateRequiredLatestStatus
 env_logger^0.6.10.11.3out of date
 k8s-openapi^0.4.00.21.1out of date
 tempfile^3.0.73.10.1up to date

Security Vulnerabilities

http: Integer Overflow in HeaderMap::reserve() can cause Denial of Service

RUSTSEC-2019-0033

HeaderMap::reserve() used usize::next_power_of_two() to calculate the increased capacity. However, next_power_of_two() silently overflows to 0 if given a sufficiently large number in release mode.

If the map was not empty when the overflow happens, the library will invoke self.grow(0) and start infinite probing. This allows an attacker who controls the argument to reserve() to cause a potential denial of service (DoS).

The flaw was corrected in 0.1.20 release of http crate.

http: HeaderMap::Drain API is unsound

RUSTSEC-2019-0034

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.