This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate aredl-backend

Dependencies

(41 total, 6 outdated, 1 insecure, 2 possibly insecure)

CrateRequiredLatestStatus
 actix-web^4.124.13.0up to date
 actix-ws^0.30.4.0out of date
 actix-rt^2.112.11.0up to date
 actix-governor^0.100.10.0up to date
 actix-cors^0.7.10.7.1up to date
 actix-http^3.73.12.0up to date
 utoipa^55.4.0up to date
 utoipa-rapidoc^66.0.0up to date
 cron^0.150.16.0out of date
 tokio^1.391.51.0up to date
 chrono ⚠️^0.40.4.44maybe insecure
 uuid^1.81.23.0up to date
 diesel^2.32.3.7up to date
 diesel_migrations^2.32.3.1up to date
 diesel-derive-enum^2.12.1.0up to date
 openidconnect^4.04.0.1up to date
 futures-util^0.30.3.32up to date
 dotenv^0.150.15.0up to date
 tracing-actix-web^0.7.190.7.21up to date
 tracing-subscriber ⚠️^0.30.3.23maybe insecure
 tracing^0.10.1.44up to date
 serial_test^33.4.0up to date
 log^0.40.4.29up to date
 listenfd^1.01.0.2up to date
 reqwest^0.120.13.2out of date
 serde^1.01.0.228up to date
 serde_json^1.01.0.149up to date
 r2d2^0.80.8.10up to date
 jsonwebtoken^10.210.3.0up to date
 strum^0.27.20.28.0out of date
 strum_macros^0.27.20.28.0out of date
 itertools^0.14.00.14.0up to date
 prometheus^0.14.00.14.0up to date
 actix-web-prom^0.10.00.10.0up to date
 rand^0.9.20.10.0out of date
 httpmock^0.8.20.8.3up to date
 regex^1.12.21.12.3up to date
 tempfile^3.23.03.27.0up to date
 async-trait^0.1.890.1.89up to date
 url^2.5.72.5.8up to date
 rsa ⚠️^0.9.100.9.10insecure

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References

rsa: Marvin Attack: potential key recovery through timing sidechannels

RUSTSEC-2023-0071

Impact

Due to a non-constant-time implementation, information about the private key is leaked through timing information which is observable over the network. An attacker may be able to use that information to recover the key.

Patches

No patch is yet available, however work is underway to migrate to a fully constant-time implementation.

Workarounds

The only currently available workaround is to avoid using the rsa crate in settings where attackers are able to observe timing information, e.g. local use on a non-compromised computer is fine.

References

This vulnerability was discovered as part of the "Marvin Attack", which revealed several implementations of RSA including OpenSSL had not properly mitigated timing sidechannel attacks.

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.