# CVE-2024-8391: Eclipse Vert.x gRPC server does not limit the maximum message size


- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 4 Sep 2024
- **Updated:** 4 Sep 2024
- **Also known as:** GHSA-g76f-gjfx-4rpr

## What is CVE-2024-8391?

CVE-2024-8391 is a medium-severity vulnerability in Eclipse Vert.x, published on 4 Sep 2024. 

### Official description

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)

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2024-8391?

4 open source packages ship an affected version, including io.vertx:vertx-grpc-client and io.vertx:vertx-grpc-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.vertx:vertx-grpc-client` | Maven | From 4.3.0 | 4.5.10 |
| `io.vertx:vertx-grpc-client` | Maven | From 4.3.0 | 4.5.10 |
| `io.vertx:vertx-grpc-server` | Maven | From 4.3.0 | 4.5.10 |
| `io.vertx:vertx-grpc-server` | Maven | From 4.3.0 | 4.5.10 |

Products: Eclipse Vert.x.

## How do I fix CVE-2024-8391?

Upgrade io.vertx:vertx-grpc-client to 4.5.10 or later.

## Is CVE-2024-8391 being exploited?

There is no known exploitation of CVE-2024-8391 in the wild and no public exploit code.

## Other vulnerabilities in Eclipse Vert.x

- [CVE-2019-17640](https://insights.sbomify.com/CVE-2019-17640/): Path Traversal in Eclipse Vert (critical 9.8)
- [CVE-2018-12542](https://insights.sbomify.com/CVE-2018-12542/): Eclipse Vert.x does not properly neutralize '' (forward slashes) sequences that can resolve to an external location (critical 9.8)
- [CVE-2018-12544](https://insights.sbomify.com/CVE-2018-12544/): Moderate severity vulnerability that affects io.vertx:vertx-core (critical 9.8)
- [CVE-2026-102469](https://insights.sbomify.com/CVE-2026-102469/): Deserialization in Eclipse Vert.x (critical 9.2)
- [CVE-2018-12540](https://insights.sbomify.com/CVE-2018-12540/): High severity vulnerability that affects io.vertx:vertx-web (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8391 and fix it if it is affected.

What it is: CVE-2024-8391 is a medium-severity vulnerability in Eclipse Vert.x, published on 4 Sep 2024. 
Exploitation: There is no known exploitation of CVE-2024-8391 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.vertx:vertx-grpc-client (Maven): affected from 4.3.0; fixed in 4.5.10
- io.vertx:vertx-grpc-client (Maven): affected from 4.3.0; fixed in 4.5.10
- io.vertx:vertx-grpc-server (Maven): affected from 4.3.0; fixed in 4.5.10
- io.vertx:vertx-grpc-server (Maven): affected from 4.3.0; fixed in 4.5.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-8391/ (Markdown: https://insights.sbomify.com/CVE-2024-8391/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8391
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8391
- OSV: https://osv.dev/vulnerability/CVE-2024-8391

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-8391/
Summaries are generated and may contain mistakes; the official description above is the record.