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.
async-graphql(49 total, 7 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-graphql-derive | ^7.0.3 | 7.0.3 | up to date |
| async-graphql-parser | ^7.0.3 | 7.0.3 | up to date |
| async-graphql-value | ^7.0.3 | 7.0.3 | up to date |
| async-stream | ^0.3.0 | 0.3.5 | up to date |
| async-trait | ^0.1.51 | 0.1.80 | up to date |
| base64 | ^0.21.0 | 0.22.1 | out of date |
| bigdecimal | >=0.3.0, <0.5.0 | 0.4.3 | up to date |
| blocking | ^1.0.2 | 1.6.0 | up to date |
| bson | ^2.4.0 | 2.10.0 | up to date |
| bytes | ^1.0.1 | 1.6.0 | up to date |
| chrono ⚠️ | ^0.4.19 | 0.4.38 | maybe insecure |
| chrono-tz | ^0.6.1 | 0.9.0 | out of date |
| fast_chemail | ^0.9.6 | 0.9.6 | up to date |
| fnv | ^1.0.7 | 1.0.7 | up to date |
| futures-channel | ^0.3.13 | 0.3.30 | up to date |
| futures-timer | ^3.0.2 | 3.0.3 | up to date |
| futures-util | ^0.3.0 | 0.3.30 | up to date |
| handlebars | ^4.3.6 | 5.1.2 | out of date |
| hashbrown | ^0.12.0 | 0.14.5 | out of date |
| http | ^1.0.0 | 1.1.0 | up to date |
| indexmap | ^2 | 2.2.6 | up to date |
| iso8601 | ^0.6.0 | 0.6.1 | up to date |
| log | ^0.4.16 | 0.4.21 | up to date |
| lru | ^0.7.1 | 0.12.3 | out of date |
| mime | ^0.3.15 | 0.3.17 | up to date |
| multer | ^3.0.0 | 3.1.0 | up to date |
| num-traits | ^0.2.14 | 0.2.19 | up to date |
| once_cell | ^1.7.2 | 1.19.0 | up to date |
| opentelemetry | ^0.21.0 | 0.22.0 | out of date |
| pin-project-lite | ^0.2.6 | 0.2.14 | up to date |
| regex | ^1.5.5 | 1.10.4 | up to date |
| rust_decimal | ^1.14.3 | 1.35.0 | up to date |
| secrecy | ^0.8.0 | 0.8.0 | up to date |
| serde | ^1.0.125 | 1.0.200 | up to date |
| serde_cbor | ^0.11.1 | 0.11.2 | up to date |
| serde_json | ^1.0.64 | 1.0.116 | up to date |
| serde_urlencoded | ^0.7.0 | 0.7.1 | up to date |
| sha2 | ^0.10.2 | 0.10.8 | up to date |
| smol_str | ^0.1.21 | 0.2.1 | out of date |
| static_assertions_next | ^1.1.1 | 1.1.2 | up to date |
| tempfile | ^3.2.0 | 3.10.1 | up to date |
| thiserror | ^1.0.24 | 1.0.59 | up to date |
| time | ^0.3.5 | 0.3.36 | up to date |
| tokio ⚠️ | ^1.17.0 | 1.37.0 | maybe insecure |
| tracing-futures | ^0.2.5 | 0.2.5 | up to date |
| tracing | ^0.1.35 | 0.1.40 | up to date |
| url | ^2.2.1 | 2.5.0 | up to date |
| uuid | ^1.0.0 | 1.8.0 | up to date |
| zxcvbn | ^2.1.2 | 2.2.2 | up to date |
(4 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.3.6 | 0.5.1 | out of date |
| futures-channel | ^0.3.13 | 0.3.30 | up to date |
| slab | ^0.4.2 | 0.4.9 | up to date |
| tokio ⚠️ | ^1.4.0 | 1.37.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);