Skip to content
Fencer Vulns
medium 6.5

CVE-2018-12541 json

Excessive memory allocation

published 2018-10-10 8 y ago modified 2026-06-17 4 mo ago also GHSA-45xm-v8gq-7jqx , EUVD-2018-0495

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.7%
EPSS 2.7% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven io.vertx:vertx-core 3.5.4
  • eclipse vert.x 3.5.4

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-12541 updated cvss 6.5

vertx: WebSocket HTTP upgrade implementation holds the entire http request in memory before the handshake

  • Red Hat JBoss Fuse 6 vertx-core
    affected: no fix planned “Out of support scope”
  • Red Hat Fuse 7.7.0
    fixed: vendor fix RHSA-2020:3192
  • Red Hat Text-Only RHOAR
    fixed: vendor fix RHSA-2018:2946

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.65% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:N/A:P
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven io.vertx:vertx-core
>=3.0.0, <3.5.4
3.5.4

Affected products

  • The Eclipse Foundation Eclipse Vert.x

Classification

Weakness
  • CWE-789 Memory Allocation with Excessive Size Value
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.