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.
ziggurat-xrpl(37 total, 16 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0 | 1.0.98 | up to date |
| async-trait | ^0.1 | 0.1.88 | up to date |
| base64 | ^0.21.0 | 0.22.1 | out of date |
| bytes | ^1 | 1.10.1 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.40 | maybe insecure |
| fs_extra | ^1.2 | 1.3.0 | up to date |
| governor | ^0.5.1 | 0.10.0 | out of date |
| hex | ^0.4 | 0.4.3 | up to date |
| histogram | ^0.7.0 | 0.11.3 | out of date |
| home | ^0.5.3 | 0.5.11 | up to date |
| httparse | ^1.7 | 1.10.1 | up to date |
| metrics | ^0.20.0 | 0.24.1 | out of date |
| metrics-util | ^0.14.0 | 0.19.0 | out of date |
| openssl ⚠️ | ^0.10 | 0.10.72 | maybe insecure |
| pea2pea | ^0.45 | 0.50.0 | out of date |
| prost | ^0.11.6 | 0.13.5 | out of date |
| rand_chacha | ^0.3 | 0.9.0 | out of date |
| serde_json | ^1.0 | 1.0.140 | up to date |
| sha2 | ^0.10 | 0.10.8 | up to date |
| tabled | ^0.10 | 0.18.0 | out of date |
| tempfile | ^3.3 | 3.19.1 | up to date |
| thiserror | ^1.0 | 2.0.12 | out of date |
| tokio-openssl | ^0.6 | 0.6.5 | up to date |
| toml | ^0.5.9 | 0.8.20 | out of date |
| bs58 | ^0.4.0 | 0.5.1 | out of date |
| clap | ^4.0.29 | 4.5.36 | up to date |
| futures-util | ^0.3 | 0.3.31 | up to date |
| jsonrpsee | ^0.16.2 | 0.24.9 | out of date |
| md5 | ^0.7 | 0.7.0 | up to date |
| rand | ^0.8 | 0.9.0 | out of date |
| reqwest | ^0.11 | 0.12.15 | out of date |
| secp256k1 | ^0.26 | 0.30.0 | out of date |
| serde | ^1 | 1.0.219 | up to date |
| tokio ⚠️ | ^1 | 1.44.2 | maybe insecure |
| tokio-util | ^0.7 | 0.7.14 | up to date |
| tracing | ^0.1 | 0.1.41 | up to date |
| tracing-subscriber | ^0.3 | 0.3.19 | up to 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);
openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.
In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).
The maintainers thank quitbug for reporting this vulnerability to us.