You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The @walletconnect/jsonrpc-ws-connection package depends on a vulnerable version of the ws package (^7.5.1). This vulnerability allows a Denial of Service (DoS) attack by sending a request with many HTTP headers, exceeding the server.maxHeadersCount threshold and causing the server to crash.
SDK Version (if relevant)
Client: JS
Version 2.13.3
To Reproduce
Steps to reproduce the behavior:
Set up a project with the @walletconnect/jsonrpc-ws-connection package.
Use the following proof of concept code to send a request with excessive headers: (from Dependabot):
Expected behavior
The @walletconnect/jsonrpc-ws-connection package should depend on a non-vulnerable version of the ws package (>=8.17.1). The server should handle requests with many HTTP headers gracefully without crashing.
Screenshots
N/A
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
The vulnerability was reported by Ryan LaPointe in websockets/ws#2230
The text was updated successfully, but these errors were encountered:
Describe the bug
The @walletconnect/jsonrpc-ws-connection package depends on a vulnerable version of the ws package (^7.5.1). This vulnerability allows a Denial of Service (DoS) attack by sending a request with many HTTP headers, exceeding the server.maxHeadersCount threshold and causing the server to crash.
SDK Version (if relevant)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The @walletconnect/jsonrpc-ws-connection package should depend on a non-vulnerable version of the ws package (>=8.17.1). The server should handle requests with many HTTP headers gracefully without crashing.
Screenshots
N/A
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
The vulnerability was reported by Ryan LaPointe in websockets/ws#2230
The text was updated successfully, but these errors were encountered: