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.
volo-thrift(19 total, 2 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1 | 1.0.82 | up to date |
| bytes | ^1 | 1.6.0 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| futures | ^0.3 | 0.3.30 | up to date |
| fxhash | ^0.2 | 0.2.1 | up to date |
| lazy_static | ^1 | 1.4.0 | up to date |
| linked-hash-map | ^0.5 | 0.5.6 | up to date |
| linkedbytes | ^0.1 | 0.1.8 | up to date |
| metainfo | ^0.7 | 0.7.9 | up to date |
| motore | ^0.4 | 0.4.1 | up to date |
| num_enum | ^0.7 | 0.7.2 | up to date |
| parking_lot | ^0.12 | 0.12.2 | up to date |
| paste | ^1 | 1.0.14 | up to date |
| pilota | ^0.10 | 0.11.0 | out of date |
| pin-project | ^1 | 1.1.5 | up to date |
| thiserror | ^1 | 1.0.59 | up to date |
| tokio ⚠️ | ^1 | 1.37.0 | maybe insecure |
| tracing | ^0.1 | 0.1.40 | up to date |
| volo | ^0.9 | 0.10.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.
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);