CVE-2024-37168

@grpc/grpc-js can allocate memory for incoming messages well above configured limits

MEDIUM

5.3

CVSS Score

Published: June 10, 2024 at 09:32 PM UTC

Updated: June 17, 2026 at 07:37 AM UTC

2 products affected across 1 vendorGrpcGrpc Node

Using grpc-node by grpc?

Get instant alerts when new vulnerabilities affect grpc-node - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.3

Exploit prediction

EPSS 0.7%

SSVC

No known exploit

Description

@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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Grpc · Grpcnpm

95%

v < 1.8.221.10.0 ≤ v < 1.10.91.9.0 ≤ v < 1.9.151.10.0 1.9.0

Affected range stops below 1.10.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.8.22, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.9.15, so it looks safe — our inference, not a vendor statement

Grpc Node · Grpc

60%

v < 1.10.9v < 1.8.22v < 1.9.15

Affected range stops below 1.10.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.8.22, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.9.15, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (4)

x_refsource_MISC

Source: [email protected]

https://github.com/grpc/grpc-node/commit/08b0422dae56467ecae1007e899efe66a8c4a650

x_refsource_MISC

Source: [email protected]

https://github.com/grpc/grpc-node/commit/674f4e351a619fd4532f84ae6dff96b8ee4e1ed3

x_refsource_MISC

Source: [email protected]

https://github.com/grpc/grpc-node/commit/a8a020339c7eab1347a343a512ad17a4aea4bfdb

x_refsource_CONFIRM

Source: [email protected]

https://github.com/grpc/grpc-node/security/advisories/GHSA-7v5v-9h63-cj86

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.3MEDIUMGitHub_M

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: NONE
Availability: LOW

Vector?

Quick Info

StatusDEFERRED

CWE

CWE-789

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card