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.
tame-oauth(10 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.13 | 0.22.0 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| http | ^0.2 | 1.1.0 | out of date |
| lock_api | ^0.4 | 0.4.12 | up to date |
| parking_lot | ^0.11 | 0.12.2 | out of date |
| ring | ^0.16 | 0.17.8 | out of date |
| serde | ^1.0 | 1.0.198 | up to date |
| serde_json | ^1.0 | 1.0.116 | up to date |
| twox-hash | ^1.5.0 | 1.6.3 | up to date |
| url | ^2.2 | 2.5.0 | up to date |
(2 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| reqwest | ^0.11 | 0.12.4 | out of date |
| tokio ⚠️ | ^1.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);