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.
wmi(8 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| chrono ⚠️ | ^0.4 | 0.4.40 | maybe insecure |
| futures | ^0.3 | 0.3.31 | up to date |
| log | ^0.4 | 0.4.26 | up to date |
| serde | ^1.0 | 1.0.219 | up to date |
| thiserror | ^2 | 2.0.12 | up to date |
| time | ^0.3 | 0.3.39 | up to date |
| windows | ^0.59 | 0.60.0 | out of date |
| windows-core | ^0.59 | 0.60.1 | out of date |
(5 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-std | ^1.10 | 1.13.0 | up to date |
| criterion | ^0.5 | 0.5.1 | up to date |
| serde_json | ^1.0 | 1.0.140 | up to date |
| tempdir | ^0.3 | 0.3.7 | up to date |
| tokio ⚠️ | ^1.20.0 | 1.44.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);