Echo
Echo: WebSocket proxy can retain connections and handlers after client disconnect
Echo is a Go web framework. From 4.15.0 until 4.16.1 and 5.4.1, Echo's Proxy middleware can retain a handler, copy goroutines, and network connections after a WebSocket client disconnects when the upstream keeps its connection open. The raw proxy waits for both copy directions without reliably closing the peer connection when one direction ends, including when a rejected upgrade response uses HTTP keep-alive. Repeated connections can accumulate resources and cause denial of service, depending on proxy-route accessibility, upstream behavior, and connection deadlines. This issue is fixed in 4.16.1 and 5.4.1.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.15.0, < 4.16.1
- >= 5.0.0, < 5.4.1
Fixed in 4.16.1, 5.4.1
Mitigation
Upgrade echo to 4.16.1 or 5.4.1 or later.
References
- Vendor advisory github.com/labstack/echo/security/advisories/G…
- Patch github.com/labstack/echo/commit/1855061e572ae9…
- Patch github.com/labstack/echo/commit/3fb0ba7e17645b…
2 more
- Release notes github.com/labstack/echo/releases/tag/v4.16.1
- Release notes github.com/labstack/echo/releases/tag/v5.4.1
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.