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

(22 total, 10 outdated, 4 possibly insecure)

CrateRequiredLatestStatus
 Inflector^0.11.40.11.4up to date
 base64^0.11.00.22.0out of date
 bytes^0.5.41.6.0out of date
 chrono ⚠️^0.4.100.4.37maybe insecure
 dirs^2.0.25.0.1out of date
 either^1.5.31.10.0up to date
 futures^0.3.40.3.30up to date
 futures-util^0.3.40.3.30up to date
 http^0.2.01.1.0out of date
 k8s-openapi^0.7.10.21.1out of date
 log^0.4.80.4.21up to date
 openssl ⚠️^0.10.280.10.64maybe insecure
 reqwest^0.10.20.12.2out of date
 rustls^0.16.00.23.4out of date
 serde^1.0.1041.0.197up to date
 serde_derive^1.0.1041.0.197up to date
 serde_json^1.0.471.0.115up to date
 serde_yaml^0.8.110.9.34+deprecatedout of date
 thiserror^1.0.101.0.58up to date
 time ⚠️^0.2.60.3.34out of date
 tokio ⚠️^0.2.131.36.0out of date
 url^2.1.12.5.0up to date

Dev dependencies

(5 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.261.0.81up to date
 env_logger^0.7.10.11.3out of date
 k8s-openapi^0.7.10.21.1out of date
 tempfile^3.1.03.10.1up to date
 tokio ⚠️^0.2.131.36.0out of date

Security Vulnerabilities

time: Potential segfault in the time crate

RUSTSEC-2020-0071

Impact

Unix-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.

The affected functions from time 0.2.7 through 0.2.22 are:

  • time::UtcOffset::local_offset_at
  • time::UtcOffset::try_local_offset_at
  • time::UtcOffset::current_local_offset
  • time::UtcOffset::try_current_local_offset
  • time::OffsetDateTime::now_local
  • time::OffsetDateTime::try_now_local

The affected functions in time 0.1 (all versions) are:

  • at
  • at_utc
  • now

Non-Unix targets (including Windows and wasm) are unaffected.

Patches

Pending a proper fix, the internal method that determines the local offset has been modified to always return None on the affected operating systems. This has the effect of returning an Err on the try_* methods and UTC on the non-try_* methods.

Users and library authors with time in their dependency tree should perform cargo update, which will pull in the updated, unaffected code.

Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.

Workarounds

A possible workaround for crates affected through the transitive dependency in chrono, is to avoid using the default oldtime feature dependency of the chrono crate by disabling its default-features and manually specifying the required features instead.

Examples:

Cargo.toml:

chrono = { version = "0.4", default-features = false, features = ["serde"] }
chrono = { version = "0.4.22", default-features = false, features = ["clock"] }

Commandline:

cargo add chrono --no-default-features -F clock

Sources:

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References

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.

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.