Eclipse Vert.x gRPC server does not limit the maximum message size
Eclipse Foundation Eclipse Vert.x
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.vertx:vertx-grpc-server Maven |
|
|
| io.vertx:vertx-grpc-client Maven |
|
|
Eclipse Foundation Eclipse Vert.x
| Product | Affected | Fixed in |
|---|---|---|
| io.vertx:vertx-grpc-server Maven |
|
|
| io.vertx:vertx-grpc-client Maven |
|
|
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)
From the CVE record · eclipse
The Eclipse Vert.x gRPC server does not limit message payload length in versions 4.3.0 through 4.5.9. A sender can submit payloads without a maximum length enforced by the server; the input does not specify authentication or user-interaction requirements. The separate io.vertx:vertx-grpc implementation based on grpc-java and Netty is not affected.
Teams using Maven packages io.vertx:vertx-grpc-server or io.vertx:vertx-grpc-client at versions >=4.3.0 and <4.5.10 should check their deployments.