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.
krustlet(12 total, 6 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0 | 1.0.100 | up to date |
| dirs-next | ^2.0.0 | 2.0.0 | up to date |
| futures | ^0.3 | 0.3.31 | up to date |
| hostname | ^0.3 | 0.4.2 | out of date |
| k8s-openapi | ^0.13 | 0.26.1 | out of date |
| krator | ^0.5 | 0.6.0 | out of date |
| kube | ^0.60 | 2.0.1 | out of date |
| oci-distribution | ^0.8 | 0.11.0 | out of date |
| regex ⚠️ | ^1.3 | 1.12.2 | maybe insecure |
| serde | ^1.0 | 1.0.228 | up to date |
| tokio ⚠️ | ^1.0 | 1.48.0 | maybe insecure |
| tracing-subscriber ⚠️ | ^0.2 | 0.3.22 | out of date |
(13 total, 6 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-trait | ^0.1 | 0.1.89 | up to date |
| compiletest_rs | ^0.6 | 0.11.2 | out of date |
| k8s-csi | ^0.4 | 0.4.0 | up to date |
| kube-runtime | ^0.60 | 2.0.1 | out of date |
| reqwest | ^0.11 | 0.12.26 | out of date |
| serde_derive | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.145 | up to date |
| tempfile | ^3.2 | 3.23.0 | up to date |
| tokio ⚠️ | ^1.0 | 1.48.0 | maybe insecure |
| tonic | ^0.5 | 0.14.2 | out of date |
| tokio-stream | ^0.1 | 0.1.17 | up to date |
| tower | ^0.4.2 | 0.5.2 | out of date |
| prost | ^0.8 | 0.14.1 | out of date |
(1 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tonic-build | ^0.5 | 0.14.2 | out of date |
kubelet(50 total, 27 outdated, 7 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0 | 1.0.100 | up to date |
| async-recursion | ^0.3 | 1.1.1 | out of date |
| async-stream | ^0.3 | 0.3.6 | up to date |
| async-trait | ^0.1 | 0.1.89 | up to date |
| base64 | ^0.13 | 0.22.1 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.42 | maybe insecure |
| dirs-next | ^2.0.0 | 2.0.0 | up to date |
| either | ^1.6 | 1.15.0 | up to date |
| futures | ^0.3 | 0.3.31 | up to date |
| hostname | ^0.3 | 0.4.2 | out of date |
| http | ^0.2 | 1.4.0 | out of date |
| hyper ⚠️ | ^0.14 | 1.8.1 | out of date |
| json-patch | ^0.2 | 4.1.0 | out of date |
| k8s-csi | ^0.4 | 0.4.0 | up to date |
| k8s-openapi | ^0.13 | 0.26.1 | out of date |
| krator | ^0.5 | 0.6.0 | out of date |
| kube | ^0.60 | 2.0.1 | out of date |
| kube-runtime | ^0.60 | 2.0.1 | out of date |
| lazy_static | ^1.4 | 1.5.0 | up to date |
| notify | ^5.0.0-pre.3 | 8.2.0 | out of date |
| oci-distribution | ^0.8 | 0.11.0 | out of date |
| prost | ^0.8 | 0.14.1 | out of date |
| prost-types | ^0.8 | 0.14.1 | out of date |
| rcgen | ^0.8 | 0.14.6 | out of date |
| regex ⚠️ | ^1.5 | 1.12.2 | maybe insecure |
| reqwest | ^0.11 | 0.12.26 | out of date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.145 | up to date |
| serde_yaml ⚠️ | ^0.8 | 0.9.34+deprecated | out of date |
| structopt | ^0.3 | 0.3.26 | up to date |
| tempfile | ^3.2 | 3.23.0 | up to date |
| thiserror | ^1.0 | 2.0.17 | out of date |
| tokio ⚠️ | ^0.2 | 1.48.0 | out of date |
| tokio-stream | ^0.1 | 0.1.17 | up to date |
| tonic | ^0.5 | 0.14.2 | out of date |
| tower | ^0.4.2 | 0.5.2 | out of date |
| tracing | ^0.1 | 0.1.44 | up to date |
| tracing-futures | ^0.2 | 0.2.5 | up to date |
| url | ^2.1 | 2.5.7 | up to date |
| uuid | ^0.8.1 | 1.19.0 | out of date |
| warp ⚠️ | ^0.3 | 0.4.2 | out of date |
| iovec | ^0.1.2 | 0.1.4 | up to date |
| kernel32-sys | ^0.2.2 | 0.2.2 | up to date |
| lazycell | ^1 | 1.3.0 | up to date |
| mio | ^0.6 | 1.1.1 | out of date |
| miow | ^0.2.1 | 0.6.1 | out of date |
| remove_dir_all ⚠️ | ^0.7.0 | 1.0.0 | out of date |
| tokio-compat-02 | ^0.2 | 0.2.0 | up to date |
| winapi | ^0.2.8 | 0.3.9 | out of date |
| ws2_32-sys | ^0.2.1 | 0.2.1 | up to date |
(8 total, 5 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| reqwest | ^0.11 | 0.12.26 | out of date |
| tempfile | ^3.1 | 3.23.0 | up to date |
| tower-test | ^0.4 | 0.4.0 | up to date |
| k8s-openapi | ^0.13 | 0.26.1 | out of date |
| bytes | ^0.3 | 1.11.0 | out of date |
| env_logger | ^0.4 | 0.11.8 | out of date |
| slab | ^0.4 | 0.4.11 | up to date |
| version-sync | ^0.5 | 0.9.5 | out of date |
(1 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tonic-build | ^0.5 | 0.14.2 | out of date |
wasi-provider(20 total, 8 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0 | 1.0.100 | up to date |
| async-trait | ^0.1 | 0.1.89 | up to date |
| backtrace | ^0.3 | 0.3.76 | up to date |
| cap-std | ^0.19 | 4.0.0 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.42 | maybe insecure |
| futures | ^0.3 | 0.3.31 | up to date |
| krator | ^0.5 | 0.6.0 | out of date |
| kube | ^0.60 | 2.0.1 | out of date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_derive | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.145 | up to date |
| tempfile | ^3.1 | 3.23.0 | up to date |
| tokio ⚠️ | ^1.0 | 1.48.0 | maybe insecure |
| tracing | ^0.1 | 0.1.44 | up to date |
| wasi-cap-std-sync | ^0.30 | 17.0.3 | out of date |
| wasi-common | ^0.30 | 39.0.1 | out of date |
| wasmtime ⚠️ | ^0.30 | 39.0.1 | out of date |
| wasmtime-wasi | ^0.30 | 39.0.1 | out of date |
| wat | ^1.0.38 | 1.243.0 | up to date |
| wasi-experimental-http-wasmtime | ^0.6.0 | 0.10.0 | out of date |
(2 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| k8s-openapi | ^0.13 | 0.26.1 | out of date |
| oci-distribution | ^0.8 | 0.11.0 | out of date |
serde_yaml: Uncontrolled recursion leads to abort in deserializationAffected versions of this crate did not properly check for recursion while deserializing aliases.
This allows an attacker to make a YAML file with an alias referring to itself causing an abort.
The flaw was corrected by checking the recursion depth.
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
No workarounds are known.
hyper: Lenient `hyper` header parsing of `Content-Length` could allow request smugglinghyper's HTTP header parser accepted, according to RFC 7230, illegal contents inside Content-Length headers.
Due to this, upstream HTTP proxies that ignore the header may still forward them along if it chooses to ignore the error.
To be vulnerable, hyper must be used as an HTTP/1 server and using an HTTP proxy upstream that ignores the header's contents
but still forwards it. Due to all the factors that must line up, an attack exploiting this vulnerability is unlikely.
hyper: Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data lossWhen decoding chunk sizes that are too large, hyper's code would encounter an integer overflow. Depending on the situation,
this could lead to data loss from an incorrect total size, or in rarer cases, a request smuggling attack.
To be vulnerable, you must be using hyper for any HTTP/1 purpose, including as a client or server, and consumers must send
requests or responses that specify a chunk size greater than 18 exabytes. For a possible request smuggling attack to be possible,
any upstream proxies must accept a chunk size greater than 64 bits.
tokio: Data race when sending and receiving after closing a `oneshot` channelIf 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.
regex: Regexes with large repetitions on empty sub-expressions take a very long time to parseThe Rust Security Response WG was notified that the regex crate did not
properly limit the complexity of the regular expressions (regex) it parses. An
attacker could use this security issue to perform a denial of service, by
sending a specially crafted regex to a service accepting untrusted regexes. No
known vulnerability is present when parsing untrusted input with trusted
regexes.
This issue has been assigned CVE-2022-24713. The severity of this vulnerability
is "high" when the regex crate is used to parse untrusted regexes. Other uses
of the regex crate are not affected by this vulnerability.
The regex crate features built-in mitigations to prevent denial of service
attacks caused by untrusted regexes, or untrusted input matched by trusted
regexes. Those (tunable) mitigations already provide sane defaults to prevent
attacks. This guarantee is documented and it's considered part of the crate's
API.
Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.
All versions of the regex crate before or equal to 1.5.4 are affected by this
issue. The fix is include starting from regex 1.5.5.
We recommend everyone accepting user-controlled regexes to upgrade immediately
to the latest version of the regex crate.
Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.
We want to thank Addison Crump for responsibly disclosing this to us according to the Rust security policy, and for helping review the fix.
We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory.
wasmtime: Bug in pooling instance allocatorbug in Wasmtime's implementation of its pooling instance allocator where when a linear memory is reused for another instance the initial heap snapshot of the prior instance can be visible, erroneously to the next instance.
Mitigations are described here.
wasmtime: Bug in Wasmtime implementation of pooling instance allocatorBug in Wasmtime's implementation of its pooling instance allocator when the allocator is configured to give WebAssembly instances a maximum of zero pages of memory.
In this configuration, the virtual memory mapping for WebAssembly memories did not meet the compiler-required configuration requirements for safely executing WebAssembly modules. Wasmtime's default settings require virtual memory page faults to indicate that wasm reads/writes are out-of-bounds, but the pooling allocator's configuration would not create an appropriate virtual memory mapping for this meaning out of bounds reads/writes can successfully read/write memory unrelated to the wasm sandbox within range of the base address of the memory mapping created by the pooling allocator.
This bug is not applicable with the default settings of the wasmtime crate.
This bug can only be triggered by setting InstanceLimits::memory_pages to zero.
This is expected to be a very rare configuration since this means that wasm modules cannot allocate any pages of linear memory.
All wasm modules produced by all current toolchains are highly likely to use linear memory, so it's expected to be unlikely that this configuration is set to zero by any production embedding of Wasmtime.
warp: Improper validation of Windows paths could lead to directory traversal attackPath resolution in warp::filters::fs::dir didn't correctly validate Windows paths
meaning paths like /foo/bar/c:/windows/web/screen/img101.png would be allowed
and respond with the contents of c:/windows/web/screen/img101.png. Thus users
could potentially read files anywhere on the filesystem.
This only impacts Windows. Linux and other unix likes are not impacted by this.
wasmtime: Miscompilation of `i8x16.swizzle` and `select` with v128 inputsThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-jqwc-c49r-4w2x. For more information see the GitHub-hosted security advisory.
wasmtime: Invalid drop of VMExternRef from partially-initialized instances in the pooling instance allocatorThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-88xq-w8cq-xfg7. For more information see the GitHub-hosted security advisory.
wasmtime: Out of bounds write in `wasmtime_trap_code` C API functionThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-h84q-m8rr-3v9q. For more information see the GitHub-hosted security advisory.
wasmtime: Data leakage between instances in the pooling allocatorThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-wh6w-3828-g9qf. For more information see the GitHub-hosted security advisory.
wasmtime: Use after free with `externref`s and epoch interruption in WasmtimeThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-gwc9-348x-qwv2. For more information see the GitHub-hosted security advisory.
wasmtime: Use After Free with `externref`s in WasmtimeThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-5fhj-g3p3-pq9g. For more information see the GitHub-hosted security advisory.
wasmtime: Miscompilation of constant values in division on AArch64This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-7f6x-jwh5-m9r4. For more information see the GitHub-hosted security advisory.
wasmtime: Out of bounds read/write with zero-memory-pages configurationThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-44mr-8vmm-wjhg. For more information see the GitHub-hosted security advisory.
tokio: reject_remote_clients Configuration corruptionOn 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.
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);
remove_dir_all: Race Condition Enabling Link Following and Time-of-check Time-of-use (TOCTOU)The remove_dir_all crate is a Rust library that offers additional features over the Rust standard library fs::remove_dir_all function.
It was possible to trick a privileged process doing a recursive delete in an attacker controlled directory into deleting privileged files, on all operating systems.
For instance, consider deleting a tree called 'etc' in a parent directory
called 'p'. Between calling remove_dir_all("a") and remove_dir_all("a")
actually starting its work, the attacker can move 'p' to 'p-prime', and
replace 'p' with a symlink to '/'. Then the privileged process deletes 'p/etc'
which is actually /etc, and now your system is broken. There are some
mitigations for this exact scenario, such as CWD relative file lookup, but
they are not guaranteed - any code using absolute paths will not have that
protection in place.
The same attack could be performed at any point in the directory tree being deleted: if 'a' contains a child directory called 'etc', attacking the deletion by replacing 'a' with a link is possible.
The new code in this release mitigates the attack within the directory tree being deleted by using file-handle relative operations: to open 'a/etc', the path 'etc' relative to 'a' is opened, where 'a' is represented by a file descriptor (Unix) or handle (Windows). With the exception of the entry points into the directory deletion logic, this is robust against manipulation of the directory hierarchy, and remove_dir_all will only delete files and directories contained in the tree it is deleting.
The entry path however is a challenge - as described above, there are some potential mitigations, but since using them must be done by the calling code, it is hard to be confident about the security properties of the path based interface.
The new extension trait RemoveDir provides an interface where it is much
harder to get it wrong.
somedir.remove_dir_contents("name-of-child").
Callers can then make their own security evaluation about how to securely get
a directory handle. That is still not particularly obvious, and we're going to
follow up with a helper of some sort (probably in the fs_at crate). Once
that is available, the path based entry points will get deprecated.
In the interim, processes that might run with elevated privileges should
figure out how to securely identify the directory they are going to delete, to
avoid the initial race. Pragmatically, other processes should be fine with the
path based entry points : this is the same interface std::fs::remove_dir_all
offers, and an unprivileged process running in an attacker controlled
directory can't do anything that the attacker can't already do.
wasmtime: Guest-controlled out-of-bounds read/write on x86\_64This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-ff4p-7xrq-q5r8. For more information see the GitHub-hosted security advisory.
wasmtime: Miscompilation of wasm `i64x2.shr_s` instruction with constant input on x86\_64This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-gw5p-q8mj-p7gh. For more information see the GitHub-hosted security advisory.
wasmtime: Undefined Behavior in Rust runtime functionsThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-ch89-5g45-qwc7. For more information see the GitHub-hosted security advisory.
wasmtime: Miscompilation of `i8x16.select` with the same inputs on x86\_64This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-xm67-587q-r2vw. For more information see the GitHub-hosted security advisory.
wasmtime: Wasmtime doesn't fully sandbox all the Windows device filenamesThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-c2f5-jxjv-2hh8. For more information see the GitHub-hosted security advisory.
tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequencesPrevious 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:
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.
wasmtime: Unsound API access to a WebAssembly shared linear memoryThis is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hc7m-r6v8-hg9q For more information see the GitHub-hosted security advisory.