Websocket Driver Node
Approved changes feed: RSS · Atom
cpe:2.3:a:faye:websocket-driver-node:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Faye (ddcbb888-6617-54eb-846a-fe19d318cc6f) |
|---|---|
| Product | Websocket Driver Node (a6d8ad26-c8c4-54d4-a593-7062215b26e3) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-54490 |
vulnerable | 2026-07-29 01:00:27.840558 |
websocket-driver: Resource limit bypass via message compression
websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.7.5, if this library is used with the permessage-deflate extension, a WebSocket server or client can be made to accept messages that are larger than the configured maximum message size because the limit is checked against the message frames' length headers, which give the size of the compressed data, not the size after decompression in lib/websocket/driver/hybi.js. This can lead to applications accepting larger messages than expected and exceeding their intended resource usage. This issue is fixed in version 0.7.5.
Published: 2026-07-17T20:54:22.417Z
Updated: 2026-07-21T02:23:58.273Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-54466 |
vulnerable | 2026-07-29 01:00:27.829901 |
websocket-driver: Message corruption via abuse of protocol length headers
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.
Published: 2026-07-17T20:53:24.769Z
Updated: 2026-07-20T19:11:09.339Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.