websocket-driver: Message corruption via abuse of protocol length headers
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-node | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Faye | Websocket-driver-node |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-xv26-6w52-cph6 | websocket-driver: Message corruption via abuse of protocol length headers |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.380% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Faye
Faye websocket-driver-node |
|
| Vendors & Products |
Faye
Faye websocket-driver-node |
| 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.7.5, the frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values 0x80 or above, a client can make the server parse these bytes into an ever-growing integer in lib/websocket/driver/draft75.js; because JavaScript numbers are 64-bit floating point values, this number will eventually lose precision and lead to the subsequent payload being parsed incorrectly. This issue is fixed in version 0.7.5. | |
| Title | websocket-driver: Message corruption via abuse of protocol length headers | |
| Weaknesses | CWE-130 | |
| References |
| |
| Metrics |
cvssV4_0
|