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.
google-apis-common(15 total, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.22 | 0.22.1 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.39 | maybe insecure |
| http | ^1 | 1.2.0 | up to date |
| http-body-util | ^0.1 | 0.1.2 | up to date |
| hyper | ^1 | 1.5.2 | up to date |
| hyper-util | ^0.1 | 0.1.10 | up to date |
| itertools | ^0.13 | 0.13.0 | up to date |
| mime | ^0.3 | 0.3.17 | up to date |
| percent-encoding | ^2 | 2.3.1 | up to date |
| serde | ^1 | 1.0.216 | up to date |
| serde_json | ^1 | 1.0.134 | up to date |
| serde_with | ^3 | 3.11.0 | up to date |
| tokio ⚠️ | ^1 | 1.42.0 | maybe insecure |
| url | ^2 | 2.5.4 | up to date |
| yup-oauth2 | ^11 | 11.0.0 | up to 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);