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.
jmap-client(14 total, 3 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ahash | ^0.8 | 0.8.12 | up to date |
| async-stream | ^0.3 | 0.3.6 | up to date |
| base64 | ^0.13 | 0.22.1 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| futures-util | ^0.3 | 0.3.32 | up to date |
| maybe-async | ^0.2 | 0.2.10 | up to date |
| parking_lot | ^0.12 | 0.12.5 | up to date |
| reqwest | ^0.12 | 0.13.2 | out of date |
| rustls ⚠️ | ^0.23 | 0.23.37 | maybe insecure |
| rustls-pki-types | ^1 | 1.14.0 | up to date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.149 | up to date |
| tokio | ^1.47 | 1.51.0 | up to date |
| tokio-tungstenite | ^0.28 | 0.29.0 | out of 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.
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.