gRPC 1.10.0
Approved changes feed: RSS · Atom
cpe:2.3:a:grpc:grpc:1.10.0:*:*:*:*:*:*:*
part: a version: 1.10.0 update: *
| Vendor | Grpc (222f4b0c-b2b5-57ff-84a2-6686580d2c60) |
|---|---|
| Product | Grpc (a93743a0-69aa-534c-8bbb-c7a5b1521ace) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/grpc/grpc |
purl2cpe | 2026-06-01 10:16:47.747008 |
pkg:github/grpc/grpc-node |
purl2cpe | 2026-06-01 10:16:47.747009 |
pkg:maven/org.webjars.npm/grpc |
purl2cpe | 2026-06-01 10:16:47.747011 |
pkg:npm/%40grpc/grpc-js |
purl2cpe | 2026-06-01 10:16:47.747012 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-37168 |
vulnerable | 2026-06-08 06:39:46.747213 |
@grpc/grpc-js can allocate memory for incoming messages well above configured limits
MEDIUM (5.3)
@grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to versions 1.10.9, 1.9.15, and 1.8.22, there are two separate code paths in which memory can be allocated per message in excess of the `grpc.max_receive_message_length` channel option: If an incoming message has a size on the wire greater than the configured limit, the entire message is buffered before it is discarded; and/or if an incoming message has a size within the limit on the wire but decompresses to a size greater than the limit, the entire message is decompressed into memory, and on the server is not discarded. This has been patched in versions 1.10.9, 1.9.15, and 1.8.22.
Published: 2024-06-10T21:32:06.403Z
Updated: 2024-08-02T03:50:55.550Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.