Echo: WebSocket proxy can retain connections and handlers after client disconnect
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| labstack | echo | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Labstack | Echo |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-9969-6676-49h5 | Echo: WebSocket proxy can retain connections and handlers after client disconnect |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.302% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Labstack
Labstack echo |
|
| Vendors & Products |
Labstack
Labstack echo |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Echo: WebSocket proxy can retain connections and handlers after client disconnect | |
| Weaknesses | CWE-772 | |
| References |
|
|
| Metrics |
cvssV4_0
|