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.
rusoto_sts(9 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-trait | ^0.1 | 0.1.80 | up to date |
| bytes | ^1.0 | 1.6.0 | up to date |
| chrono ⚠️ | ^0.4.0 | 0.4.38 | maybe insecure |
| futures | ^0.3 | 0.3.30 | up to date |
| rusoto_core | ^0.46.0 | 0.48.0 | out of date |
| serde | ^1.0.2 | 1.0.198 | up to date |
| serde_derive | ^1.0.2 | 1.0.198 | up to date |
| serde_urlencoded | ^0.6 | 0.7.1 | out of date |
| xml-rs | ^0.8 | 0.8.20 | up to date |
(3 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| rusoto_mock | ^0.46.0 | 0.48.0 | out of date |
| tempfile | ^3.1.0 | 3.10.1 | up to 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);