vertx: WebSocket HTTP upgrade implementation holds the entire http request in memory before the handshake
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| The Eclipse Foundation | Eclipse Vert.x | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Fuse 7.7.0 | |||
| vertx-core | cpe:/a:redhat:jboss_fuse:7 | RHSA-2020:3192 | 2020-07-28T00:00:00Z |
| Text-Only RHOAR | |||
| vert-core | cpe:/a:redhat:openshift_application_runtimes:1.0 | RHSA-2018:2946 | 2018-10-18T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2018-0495 | In version from 3.0.0 to 3.5.3 of Eclipse Vert.x, the WebSocket HTTP upgrade implementation buffers the full http request before doing the handshake, holding the entire request body in memory. There should be a reasonnable limit (8192 bytes) above which the WebSocket gets an HTTP response with the 413 status code and the connection gets closed. |
Github GHSA |
GHSA-45xm-v8gq-7jqx | Excessive memory allocation |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 2.7% (2.652% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.