Skip to content
Fencer Intel
high 7.5

CVE-2024-8391 json

Eclipse Vert.x gRPC server does not limit the maximum message size

published 2y ago modified 4mo ago also EUVD-2024-2795 , GHSA-g76f-gjfx-4rpr

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

Summary

In Eclipse Vert.x version 4.3.0 to 4.5.9, the gRPC server does not limit the maximum length of message payload (Maven GAV: io.vertx:vertx-grpc-server and io.vertx:vertx-grpc-client).

This is fixed in the 4.5.10 version.

Note this does not affect the Vert.x gRPC server based grpc-java and Netty libraries (Maven GAV: io.vertx:vertx-grpc)

Patch / fix

  • maven io.vertx:vertx-grpc-server 4.5.10
  • maven io.vertx:vertx-grpc-client 4.5.10
  • Eclipse Foundation Eclipse Vert.x 4.5.10
  • eclipse_foundation vert.x 4.5.10

Is CVE-2024-8391 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2024-8391 updated cvss 7.5

io.vertx:vertx-grpc-client: io.vertx:vertx-grpc-server: Vertx gRPC server does not limit the maximum message size

  • Red Hat OpenShift Serverless vertx-grpc-client Red Hat build of Quarkus io.vertx.vertx-grpc-server io.vertx.vertx-grpc-server
    affected: workaround, no fix available
  • Red Hat JBoss Enterprise Application Platform 8 vertx-grpc-client, vertx-grpc-server
    affected: workaround, no fix planned “Will not fix”
  • Red Hat JBoss Enterprise Application Platform Expansion Pack vertx-grpc
    affected: workaround, no fix available
  • Red Hat build of Apache Camel 4 for Quarkus 3
    fixed: vendor fix RHSA-2024:7052
  • Red Hat build of Quarkus 3.8.6.redhat vertx-grpc-client 4.5.7.redhat-00003, vertx-grpc-server 4.5.7.redhat-00003
    fixed: vendor fix RHSA-2024:6437
  • Red Hat JBoss EAP XP 5.0 Update 1.0
    fixed: vendor fix RHSA-2025:0542
  • Red Hat OpenShift Serverless 1.34 openshift-serverless-1/logic-rhel8-operator 1.34.0-5, openshift-serverless-1/logic-operator-bundle 1.34.0-5, openshift-serverless-1/logic-swf-builder-rhel8 1.34.0-6, openshift-serverless-1/logic-swf-devmode-rhel8 1.34.0-6, openshift-serverless-1/logic-management-console-rhel8 1.34.0-5, openshift-serverless-1/logic-data-index-ephemeral-rhel8 1.34.0-6, +4 more
    fixed: vendor fix RHSA-2024:8023
  • Red Hat build of Quarkus 3.8.6.redhat jna 5.8.0, lit 3.1.2, db2 1.19.6, h2 2.2.224, y18n 5.0.8, bson 4.11.1, +959 more
    not affected: vulnerable code not present

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

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 4.0 6.9 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
GitHub 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L
CNA 4.0 6.9 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven io.vertx:vertx-grpc-server
>=4.3.0, <4.5.10
4.5.10
maven io.vertx:vertx-grpc-client
>=4.3.0, <4.5.10
4.5.10

Affected products

  • Eclipse Foundation Eclipse Vert.x
  • eclipse_foundation vert.x

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel 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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.