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 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| futures | ^0.3 | 0.3.32 | up to date |
| log | ^0.4 | 0.4.29 | up to date |
| serde | ^1.0 | 1.0.228 | up to date |
| thiserror | ^2 | 2.0.18 | up to date |
| time ⚠️ | ^0.3 | 0.3.47 | maybe insecure |
| windows | >=0.59, <0.63 | 0.62.2 | up to date |
| windows-core | >=0.59, <0.63 | 0.62.2 | up to date |
(6 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-std | ^1 | 1.13.2 | up to date |
| criterion | ^0.8 | 0.8.2 | up to date |
| rusty-fork | ^0.3.0 | 0.3.1 | up to date |
| serde_json | ^1.0 | 1.0.149 | up to date |
| tempdir | ^0.3 | 0.3.7 | up to date |
| tokio ⚠️ | ^1 | 1.49.0 | 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);
time: Denial of Service via Stack ExhaustionWhen user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.
A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.
Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.