websocket-driver: Memory exhaustion in HTTP header parser
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| faye | websocket-driver-ruby | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Faye | Websocket-driver-ruby |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-8j3g-f24p-4mpw | websocket-driver: Memory exhaustion in HTTP header parser |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.488% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Faye
Faye websocket-driver-ruby |
|
| Vendors & Products |
Faye
Faye websocket-driver-ruby |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, when websocket-driver is used to implement a WebSocket server on top of a TCP server using WebSocket::Driver.server() or to complement a WebSocket client, a peer can make a single connection consume an unbounded amount of memory by sending an HTTP request or response with a never-ending list of headers. This can lead to the receiving process running out of memory. This issue is fixed in version 0.8.1. | |
| Title | websocket-driver: Memory exhaustion in HTTP header parser | |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
cvssV4_0
|