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.
libosu(25 total, 8 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bitflags | ^1.3.2 | 2.5.0 | out of date |
| lazy_static | ^1.4.0 | 1.4.0 | up to date |
| num | ^0.4.0 | 0.4.2 | up to date |
| num-derive | ^0.3.3 | 0.4.2 | out of date |
| num-traits | ^0.2.15 | 0.2.18 | up to date |
| ordered-float | ^3.0.0 | 4.2.0 | out of date |
| regex | ^1.6.0 | 1.10.4 | up to date |
| thiserror | ^1.0.31 | 1.0.59 | up to date |
| derive_more | ^0.99.17 | 0.99.17 | up to date |
| log | ^0.4.17 | 0.4.21 | up to date |
| byteorder | ^1.4.3 | 1.5.0 | up to date |
| static_assertions | ^1.1.0 | 1.1.0 | up to date |
| futures | ^0.3.21 | 0.3.30 | up to date |
| http | ^0.2.8 | 1.1.0 | out of date |
| hyper | ^0.14.20 | 1.3.1 | out of date |
| tokio ⚠️ | ^1.17.0 | 1.37.0 | maybe insecure |
| xz2 | ^0.1.6 | 0.1.7 | up to date |
| lzma-rs | ^0.2 | 0.3.0 | out of date |
| serde | ^1.0.136 | 1.0.198 | up to date |
| serde_json | ^1.0.79 | 1.0.116 | up to date |
| reqwest | ^0.11.10 | 0.12.4 | out of date |
| anyhow | ^1.0.56 | 1.0.82 | up to date |
| chrono ⚠️ | ^0.4.19 | 0.4.38 | maybe insecure |
| url | ^2.2.2 | 2.5.0 | up to date |
| rosu-pp | ^0.8.0 | 1.0.0 | out of date |
(5 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| serde_json | ^1.0.82 | 1.0.116 | up to date |
| difference | ^2.0.0 | 2.0.0 | up to date |
| anyhow | ^1.0.58 | 1.0.82 | up to date |
| proptest | ^1.0.0 | 1.4.0 | up to date |
| proptest-derive | ^0.3.0 | 0.4.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);