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.
hermod-api(27 total, 17 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix | ^0.12.0-beta | 0.13.3 | out of date |
| actix-web | ^4.0.0-beta.3 | 4.5.1 | up to date |
| tokio ⚠️ | ^1.10.1 | 1.37.0 | maybe insecure |
| serde-aux | ^2.3.0 | 4.5.0 | out of date |
| serde | ^1.0 | 1.0.201 | up to date |
| uuid | ^0.8 | 1.8.0 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| serde_json | ^1.0.67 | 1.0.117 | up to date |
| anyhow | ^1.0.43 | 1.0.83 | up to date |
| base64 | ^0.13 | 0.22.1 | out of date |
| thiserror | ^1.0.29 | 1.0.60 | up to date |
| config | ^0.11.0 | 0.14.0 | out of date |
| argon2 | ^0.3 | 0.5.3 | out of date |
| rand | ^0.8 | 0.8.5 | up to date |
| tracing | ^0.1.26 | 0.1.40 | up to date |
| tracing-bunyan-formatter | ^0.2.5 | 0.3.9 | out of date |
| tracing-log | ^0.1.2 | 0.2.0 | out of date |
| tracing-subscriber | ^0.2.20 | 0.3.18 | out of date |
| actix-cors | ^0.6.0-beta.2 | 0.7.0 | out of date |
| jsonwebtoken | ^7.2.0 | 9.3.0 | out of date |
| opentelemetry | ^0.16 | 0.22.0 | out of date |
| opentelemetry-otlp | ^0.9 | 0.15.0 | out of date |
| tracing-opentelemetry | ^0.15.0 | 0.23.0 | out of date |
| tracing-actix-web | ^0.4.0-beta.15 | 0.7.10 | out of date |
| reqwest | ^0.11 | 0.12.4 | out of date |
| urlencoding | ^2.1.0 | 2.1.3 | up to date |
| sqlx | ^0.5.7 | 0.7.4 | out of date |
(3 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-rt | ^2.0.2 | 2.9.0 | up to date |
| once_cell | ^1.7.2 | 1.19.0 | up to date |
| wiremock | ^0.5 | 0.6.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);