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.
poem-openapi(26 total, 6 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.21.0 | 0.22.1 | out of date |
| bson | ^2.0.0 | 2.14.0 | up to date |
| bytes | ^1.1.0 | 1.10.1 | up to date |
| chrono ⚠️ | ^0.4.19 | 0.4.41 | maybe insecure |
| derive_more | ^0.99.16 | 2.0.1 | out of date |
| email_address | ^0.2.1 | 0.2.9 | up to date |
| futures-util | ^0.3.17 | 0.3.31 | up to date |
| hostname-validator | ^1.1.0 | 1.1.1 | up to date |
| humantime | ^2.1.0 | 2.2.0 | up to date |
| ipnet | ^2.7.1 | 2.11.0 | up to date |
| mime | ^0.3.16 | 0.3.17 | up to date |
| num-traits | ^0.2.14 | 0.2.19 | up to date |
| poem | ^1.3.56 | 3.1.10 | out of date |
| poem-openapi-derive | ^2.0.27 | 5.1.14 | out of date |
| quick-xml | =0.26.0 | 0.37.5 | out of date |
| regex | ^1.5.5 | 1.11.1 | up to date |
| rust_decimal | ^1.22.0 | 1.37.1 | up to date |
| serde | ^1.0.130 | 1.0.219 | up to date |
| serde_json | ^1.0.68 | 1.0.140 | up to date |
| serde_urlencoded | ^0.7.1 | 0.7.1 | up to date |
| serde_yaml | ^0.9 | 0.9.34+deprecated | up to date |
| thiserror | ^1.0.30 | 2.0.12 | out of date |
| time | ^0.3.9 | 0.3.41 | up to date |
| tokio ⚠️ | ^1.17.0 | 1.45.0 | maybe insecure |
| url | ^2.2.2 | 2.5.4 | up to date |
| uuid | ^1.1.0 | 1.16.0 | up to date |
(2 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| poem | ^1.3.56 | 3.1.10 | out of date |
| tokio ⚠️ | ^1.17.0 | 1.45.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);