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.
rust-nebula(21 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.65 | 1.0.93 | up to date |
| async-compat | ^0.2 | 0.2.4 | up to date |
| async-sleep | ^0.4 | 0.4.1 | up to date |
| async-trait | ^0.1 | 0.1.83 | up to date |
| base64 | ^0.11.0 | 0.22.1 | out of date |
| bb8 | ^0.8.5 | 0.8.6 | up to date |
| bufsize | ^1.0 | 1.0.8 | up to date |
| bytes | ^1.1 | 1.8.0 | up to date |
| const-cstr | ^0.3 | 0.3.0 | up to date |
| futures | ^0.3 | 0.3.31 | up to date |
| futures-util | ^0.3 | 0.3.31 | up to date |
| ghost | ^0.1 | 0.1.17 | up to date |
| num-derive | ^0.3.3 | 0.4.2 | out of date |
| num-traits | ^0.2 | 0.2.19 | up to date |
| ordered-float | ^1.1.1 | 4.5.0 | out of date |
| panic-message | ^0.3 | 0.3.0 | up to date |
| serde | ^1 | 1.0.215 | up to date |
| serde_json | ^1.0.79 | 1.0.132 | up to date |
| thiserror | ^1.0.36 | 2.0.3 | out of date |
| tokio ⚠️ | ^1 | 1.41.1 | maybe insecure |
| tracing | ^0.1 | 0.1.40 | up to date |
(6 total, 2 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| float-cmp | ^0.9 | 0.10.0 | out of date |
| futures-lite | ^1 | 2.5.0 | out of date |
| quickcheck | ^1.0 | 1.0.3 | up to date |
| serde_repr | ^0.1 | 0.1.19 | up to date |
| tokio ⚠️ | ^1 | 1.41.1 | maybe insecure |
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);