Echo denial of service in Proxy WebSocket connections
labstack echo
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/labstack/echo/v4 Go |
|
|
| github.com/labstack/echo/v5 Go |
|
|
labstack echo
| Product | Affected | Fixed in |
|---|---|---|
| github.com/labstack/echo/v4 Go |
|
|
| github.com/labstack/echo/v5 Go |
|
|
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.
From the CVE record · GitHub_M
Echo's Proxy middleware can retain handlers, copy goroutines, and network connections after a WebSocket client disconnects if the upstream keeps its connection open. Repeated connections to an accessible proxy route can exhaust resources and cause denial of service, depending on upstream behavior and connection deadlines.
Check deployments using github.com/labstack/echo/v4 versions >=4.15.0 and <4.16.1 or github.com/labstack/echo/v5 versions >=5.0.0 and <5.4.1.