Websocket Driver Ruby
Approved changes feed: RSS · Atom
cpe:2.3:a:faye:websocket-driver-ruby:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Faye (ddcbb888-6617-54eb-846a-fe19d318cc6f) |
|---|---|
| Product | Websocket Driver Ruby (64ebac4d-8fd0-57d7-9417-ee8a02ac6818) |
| 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-54465 |
vulnerable | 2026-07-29 01:00:27.826908 |
websocket-driver: Memory exhaustion in HTTP header parser
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.
Published: 2026-07-17T20:06:06.980Z
Updated: 2026-07-20T13:49:17.424Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-54464 |
vulnerable | 2026-07-29 01:00:27.826593 |
websocket-driver: Resource limit bypass via message compression
### Impact
If this library is used in tandem 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. This is because this limit is checked
against the message frames' length headers, which give the size of the
compressed data, not the size after decompression. This can lead to applications
accepting larger messages than expected and exceeding their intended resource
usage.
### Patches
The issue has been patched in version 0.8.1, by checking the length of messages
after they are processed by incoming extensions. All users should upgrade to
this version.
### Workarounds
No known workarounds exist.
### Acknowledgements
This issue was discovered and reported by Pranjali Thakur, DepthFirst Security
Research Team.
Published: 2026-07-17T20:03:36.326Z
Updated: 2026-07-21T02:13:20.815Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-54463 |
vulnerable | 2026-07-29 01:00:27.826309 |
websocket-driver: Memory exhaustion via abuse of protocol length headers
websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, draft versions of the WebSocket protocol in websocket-driver include a length header that allows an arbitrarily large integer to be encoded as bytes with the high bit set, and a server or client can send an indefinite sequence of 0x80 or higher bytes that the peer parses into an ever-growing Ruby integer. This can make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory. This issue is fixed in version 0.8.1.
Published: 2026-07-17T20:05:17.888Z
Updated: 2026-07-20T16:58:33.914Z |
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.