Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

tls-listener

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5crates.ioPublished

    tls-listener affected by the slow loris vulnerability with default configuration

    CVE-2024-28854 · GHSA-2qph-qpvm-2qf7

    Affected
    • crates.io tls-listener <= 0.9.1
    Fixed in
    0.10.0· Vendor fix available
    Issue
    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. Details The default configuration options make any public service using TlsListener::new() vulnerable to a slow-loris DoS attack. PoC Running the HTTP TLS server example: https://github.com/tmccombs/tls-listener/blob/6c57dea2d9beb1577ae4d80f6eaf03aad4ef3857/examples/http.rs, then running the following script will prevent new connections to the server. Impact This is an instance of a slow-loris attack). This impacts any publically accessible service using the default configuration of tls-listener Mitigation Previous versions can mitigate this by passing a large value, such as usize::MAX as the parameter to Builder::maxhandshakes.

    Recommended action: Upgrade to 0.10.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →