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.
clickhouse(26 total, 1 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bstr | ^1.11.0 | 1.12.0 | up to date |
| bytes | ^1.5.0 | 1.10.1 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.41 | maybe insecure |
| cityhash-rs | =1.0.1 | 1.0.1 | up to date |
| clickhouse-derive | ^0.2.0 | 0.2.0 | up to date |
| futures | ^0.3.5 | 0.3.31 | up to date |
| futures-channel | ^0.3.30 | 0.3.31 | up to date |
| http-body-util | ^0.1.2 | 0.1.3 | up to date |
| hyper | ^1.4 | 1.6.0 | up to date |
| hyper-rustls | ^0.27.3 | 0.27.5 | up to date |
| hyper-tls | ^0.6.0 | 0.6.0 | up to date |
| hyper-util | ^0.1.6 | 0.1.11 | up to date |
| lz4_flex | ^0.11.3 | 0.11.3 | up to date |
| quanta | ^0.12 | 0.12.5 | up to date |
| replace_with | ^0.1.7 | 0.1.7 | up to date |
| rustls ⚠️ | ^0.23 | 0.23.27 | maybe insecure |
| sealed | ^0.6 | 0.6.0 | up to date |
| serde | ^1.0.106 | 1.0.219 | up to date |
| serde_json | ^1.0.68 | 1.0.140 | up to date |
| sha-1 | ^0.10 | 0.10.1 | up to date |
| static_assertions | ^1.1 | 1.1.0 | up to date |
| thiserror | ^1.0.16 | 2.0.12 | out of date |
| time | ^0.3 | 0.3.41 | up to date |
| tokio ⚠️ | ^1.0.1 | 1.45.0 | maybe insecure |
| url | ^2.1.1 | 2.5.4 | up to date |
| uuid | ^1 | 1.16.0 | up to date |
(11 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.5.0 | 0.5.1 | up to date |
| fixnum | ^0.9.2 | 0.9.3 | up to date |
| hyper | ^1.1 | 1.6.0 | up to date |
| rand | ^0.8.5 | 0.9.1 | out of date |
| serde | ^1.0.106 | 1.0.219 | up to date |
| serde_bytes | ^0.11.4 | 0.11.17 | up to date |
| serde_json | ^1 | 1.0.140 | up to date |
| serde_repr | ^0.1.7 | 0.1.20 | up to date |
| time | ^0.3.17 | 0.3.41 | up to date |
| tokio ⚠️ | ^1.0.1 | 1.45.0 | maybe insecure |
| uuid | ^1 | 1.16.0 | up to date |
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.
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);
rustls: rustls network-reachable panic in `Acceptor::accept`A bug introduced in rustls 0.23.13 leads to a panic if the received
TLS ClientHello is fragmented. Only servers that use
rustls::server::Acceptor::accept() are affected.
Servers that use tokio-rustls's LazyConfigAcceptor API are affected.
Servers that use tokio-rustls's TlsAcceptor API are not affected.
Servers that use rustls-ffi's rustls_acceptor_accept API are affected.