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.
organism-planning(12 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1 | 1.0.104 | up to date |
| async-trait | ^0.1 | 0.1.91 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.45 | maybe insecure |
| converge-kernel | ^3.9.3 | 3.9.3 | up to date |
| converge-pack | ^3.9.3 | 3.9.3 | up to date |
| converge-provider | ^3.9.3 | 3.9.3 | up to date |
| organism-intent | ^1.9.4 | 1.9.4 | up to date |
| converge-prism-analytics | ^2.0.2 | 2.0.3 | up to date |
| serde | ^1 | 1.0.229 | up to date |
| serde_json | ^1 | 1.0.151 | up to date |
| thiserror | ^2 | 2.0.19 | up to date |
| uuid | ^1 | 1.24.0 | up to date |
(2 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| proptest | ^1 | 1.11.0 | up to date |
| tokio ⚠️ | ^1 | 1.53.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);