websocket-driver: Resource limit bypass via message compression
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.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Faye | Websocket-driver-ruby |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-33ph-fccm-39pj | websocket-driver: Resource limit bypass via message compression |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.445% 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 | ### 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. | |
| Title | websocket-driver: Resource limit bypass via message compression | |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
cvssV4_0
|