RUSTSEC-2024-0341: Slow loris vulnerability with default configuration

What to do

1. See which version you have: cargo tree -i tls-listener (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p tls-listener. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example tls-listener = "0.10.0") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

tls-listener is a rust lang wrapper around a connection listener to support TLS. With the default configuration of tls-listener, a malicious user can open 6.4 TcpStreams a second, sending 0 bytes, and can trigger a DoS. The default configuration options make any public service using TlsListener::new() vulnerable to a slow-loris DoS attack. This impacts any publicly accessible service using the default configuration of tls-listener in versions prior to 0.10.0. Users are advised to upgrade. Users unable to upgrade may mitigate this by passing a large value, such as usize::MAX as the parameter to Builder::max_handshakes.

References

• Package: crates.io/crates/tls-listener
• Advisory: rustsec.org/advisories/RUSTSEC-2024-0341.html
• Web: github.com/tmccombs/tls-listener/commit/d5a7655d6ea9e53ab57c3013092c5576da964bc4

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.