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 quinn

Dependencies

(12 total, 6 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-io^1.62.6.0out of date
 async-std^1.111.13.2up to date
 bytes^11.11.0up to date
 futures-io^0.3.190.3.31up to date
 pin-project-lite^0.20.2.16up to date
 quinn-proto ⚠️^0.10.20.11.13out of date
 rustc-hash^1.12.1.1out of date
 rustls ⚠️^0.21.00.23.35out of date
 thiserror^1.0.212.0.17out of date
 tokio^1.28.11.48.0up to date
 tracing^0.1.100.1.43up to date
 quinn-udp^0.40.5.14out of date

Dev dependencies

(12 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.221.0.100up to date
 bencher^0.1.50.1.5up to date
 clap^44.5.53up to date
 crc^33.4.0up to date
 directories-next^22.0.0up to date
 rand^0.80.9.2out of date
 rcgen^0.10.00.14.6out of date
 rustls-pemfile^1.0.02.2.0out of date
 tokio^1.28.11.48.0up to date
 tracing-futures^0.2.00.2.5up to date
 tracing-subscriber ⚠️^0.3.00.3.22maybe insecure
 url^22.5.7up to date

Security Vulnerabilities

quinn-proto: Denial of service in Quinn servers

RUSTSEC-2023-0063

Receiving QUIC frames containing a frame with unknown frame type could lead to a panic. Unfortunately this is issue was not found by our fuzzing infrastructure.

Thanks to the QUIC Tester research group for reporting this issue.

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.

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.