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.

Crate rustfulapi

Dependencies

(45 total, 13 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 axum^0.8.10.8.9up to date
 axum-extra^0.10.00.12.6out of date
 sea-orm^1.1.21.1.20up to date
 sea-orm-migration^1.1.21.1.20up to date
 anyhow^1.0.941.0.102up to date
 argon2^0.5.30.5.3up to date
 base64^0.22.10.22.1up to date
 chrono^0.4.390.4.44up to date
 config^0.15.80.15.22up to date
 fake^4.0.05.1.0out of date
 futures^0.3.310.3.32up to date
 itertools^0.14.00.14.0up to date
 jsonwebtoken^9.3.010.3.0out of date
 lettre^0.11.110.11.21up to date
 log^0.4.220.4.29up to date
 log-derive^0.4.10.4.1up to date
 openssl ⚠️^0.10.680.10.78maybe insecure
 rand^0.9.00.10.1out of date
 rand_core^0.9.20.10.1out of date
 redis^0.29.01.2.0out of date
 reqwest^0.12.90.13.3out of date
 scraper^0.23.10.26.0out of date
 sentry^0.36.00.48.0out of date
 serde^1.0.2151.0.228up to date
 serde_json^1.0.1331.0.149up to date
 sha2^0.10.80.11.0out of date
 strum^0.27.10.28.0out of date
 tera^1.20.01.20.1up to date
 test-context^0.4.10.5.8out of date
 thiserror^2.0.112.0.18up to date
 tokio^1.42.01.52.1up to date
 tracing^0.1.410.1.44up to date
 tracing-appender^0.2.30.2.5up to date
 tracing-bunyan-formatter^0.3.100.3.10up to date
 tracing-log^0.2.00.2.0up to date
 tracing-subscriber ⚠️^0.3.190.3.23maybe insecure
 url^2.5.22.5.8up to date
 utoipa^5.2.05.4.0up to date
 utoipa-swagger-ui^9.0.09.0.2up to date
 utoipa-axum^0.2.00.2.0up to date
 uuid^1.11.01.23.1up to date
 tokio-tungstenite^0.26.20.29.0out of date
 garde^0.22.00.22.1up to date
 regex^1.11.11.12.3up to date
 wiremock^0.6.20.6.5up to date

Security Vulnerabilities

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

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.

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous 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:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

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.