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 quickie

Dependencies

(9 total, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.89up to date
 bytes^11.11.0up to date
 futures-util^0.30.3.31up to date
 parking_lot^0.120.12.5up to date
 quinn^0.110.11.9up to date
 quinn-proto ⚠️^0.110.11.13maybe insecure
 tokio^1.241.48.0up to date
 tokio-util^0.70.7.17up to date
 tracing^0.10.1.41up to date

Dev dependencies

(10 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 deadline^0.20.2.0up to date
 humansize^22.1.3up to date
 libp2p^0.540.56.0out of date
 libp2p-tls^0.50.6.2out of date
 libp2p-quic^0.110.13.0out of date
 peak_alloc^0.20.3.0out of date
 rcgen^0.130.14.5out of date
 rustls ⚠️^0.23.120.23.35maybe insecure
 tokio^1.241.48.0up to date
 tracing-subscriber ⚠️^0.30.3.20maybe insecure

Security Vulnerabilities

quinn-proto: `Endpoint::retry()` calls can lead to panicking

RUSTSEC-2024-0373

In 0.11.0, we overhauled the server-side Endpoint implementation to enable more careful handling of incoming connection attempts. However, some of the code paths that cleaned up state after connection attempts were processed confused the initial destination connection ID with the destination connection ID of a substantial package. This resulted in the internal Endpoint state becoming inconsistent, which could then lead to a panic.

https://github.com/quinn-rs/quinn/commit/e01609ccd8738bd438d86fa7185a0f85598cb58f

Thanks to @finbear for reporting and investingating, and to @BiagoFesta for coordinating.

rustls: rustls network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

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