Hub: Unauthenticated WebSocket RPC Waiter Resource Exhaustion
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| anephenix | hub | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Anephenix | Hub |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-g5vv-q72c-7j78 | @anephenix/hub: Unauthenticated WebSocket RPC Waiter Resource Exhaustion |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.609% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Anephenix
Anephenix hub |
|
| Vendors & Products |
Anephenix
Anephenix hub |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Hub is a Node.js WebSocket server and client with added features. Prior to 0.2.16, every incoming unauthenticated WebSocket connection triggers loadDefaultConnectionEventListeners to call requestClientId, which calls rpc.send for the get-client-id action and pushes a request into RPC.requests. The RPC.waitForReply function starts a setInterval polling loop every 10 milliseconds that is cleared only after a matching reply; if the client remains silent and closes, the timer and pending request stay allocated because the socket close path does not cancel them. Repeated connections therefore cause unbounded timers and heap entries, exhausting CPU and memory and making the server unavailable. This issue is fixed in version 0.2.16. | |
| Title | Hub: Unauthenticated WebSocket RPC Waiter Resource Exhaustion | |
| Weaknesses | CWE-400 | |
| References |
| |
| Metrics |
cvssV3_1
|