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.
status-list-server(47 total, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tokio ⚠️ | ^1 | 1.48.0 | maybe insecure |
| async-trait | ^0.1 | 0.1.89 | up to date |
| hyper | ^1.7 | 1.8.1 | up to date |
| hyper-util | ^0.1 | 0.1.18 | up to date |
| reqwest | ^0.12 | 0.12.24 | up to date |
| tower | ^0.5 | 0.5.2 | up to date |
| hyper-rustls | ^0.27 | 0.27.7 | up to date |
| axum | ^0.8 | 0.8.7 | up to date |
| tower-http | ^0.6 | 0.6.7 | up to date |
| sea-orm | ^1.1 | 1.1.19 | up to date |
| sea-orm-migration | ^1.1 | 1.1.19 | up to date |
| moka | ^0.12 | 0.12.11 | up to date |
| rand | ^0.9 | 0.9.2 | up to date |
| pem | ^3 | 3.0.6 | up to date |
| coset | ^0.4 | 0.4.0 | up to date |
| instant-acme | ^0.8 | 0.8.4 | up to date |
| rustls ⚠️ | ^0.23 | 0.23.35 | maybe insecure |
| webpki-roots | ^1 | 1.0.4 | up to date |
| rustls-pki-types | ^1.13 | 1.13.1 | up to date |
| secrecy | ^0.10 | 0.10.3 | up to date |
| rcgen | ^0.14 | 0.14.5 | up to date |
| jsonwebtoken | ^10 | 10.2.0 | up to date |
| serde_json | ^1.0 | 1.0.145 | up to date |
| serde-aux | ^4 | 4.7.0 | up to date |
| serde | ^1.0 | 1.0.228 | up to date |
| config | ^0.15 | 0.15.19 | up to date |
| dotenvy | ^0.15 | 0.15.7 | up to date |
| aws-config | ^1 | 1.8.11 | up to date |
| aws-sdk-s3 | ^1 | 1.115.0 | up to date |
| aws-sdk-route53 | ^1 | 1.103.0 | up to date |
| aws-sdk-secretsmanager | ^1 | 1.95.0 | up to date |
| aws_secretsmanager_caching | ^2 | 2.0.0 | up to date |
| tracing | ^0.1 | 0.1.43 | up to date |
| tracing-subscriber ⚠️ | ^0.3 | 0.3.22 | maybe insecure |
| thiserror | ^2.0 | 2.0.17 | up to date |
| color-eyre | ^0.6 | 0.6.5 | up to date |
| uuid | ^1 | 1.18.1 | up to date |
| base64 | ^0.22 | 0.22.1 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.42 | maybe insecure |
| base64url | ^0.1 | 0.1.0 | up to date |
| flate2 | ^1.1 | 1.1.5 | up to date |
| x509-parser | ^0.18 | 0.18.0 | up to date |
| public-suffix | ^0.1 | 0.1.3 | up to date |
| tokio-cron-scheduler | ^0.15 | 0.15.1 | up to date |
| redis | ^0.32 | 0.32.7 | up to date |
| p256 | ^0.13 | 0.13.2 | up to date |
| tikv-jemallocator | ^0.6 | 0.6.1 | up to date |
(2 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| sealed_test | ^1.1.0 | 1.1.0 | up to date |
| sea-orm | ^1.1 | 1.1.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);
rustls: rustls network-reachable panic in `Acceptor::accept`A bug introduced in rustls 0.23.13 leads to a panic if the received
TLS ClientHello is fragmented. Only servers that use
rustls::server::Acceptor::accept() are affected.
Servers that use tokio-rustls's LazyConfigAcceptor API are affected.
Servers that use tokio-rustls's TlsAcceptor API are not affected.
Servers that use rustls-ffi's rustls_acceptor_accept API are affected.
tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequencesPrevious versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:
In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.
This was patched in PR #3368 to escape ANSI control characters from user input.