Skip to content

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

Moderate severity GitHub Reviewed Published Jun 10, 2024 in grpc/grpc-node • Updated Jun 11, 2024

Package

npm @grpc/grpc-js (npm)

Affected versions

>= 1.10.0, < 1.10.9
>= 1.9.0, < 1.9.15
< 1.8.22

Patched versions

1.10.9
1.9.15
1.8.22

Description

Impact

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:

  1. If an incoming message has a size on the wire greater than the configured limit, the entire message is buffered before it is discarded.
  2. 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.

Patches

This has been patched in versions 1.10.9, 1.9.15, and 1.8.22

References

@murgatroid99 murgatroid99 published to grpc/grpc-node Jun 10, 2024
Published to the GitHub Advisory Database Jun 10, 2024
Reviewed Jun 10, 2024
Published by the National Vulnerability Database Jun 10, 2024
Last updated Jun 11, 2024

Severity

Moderate
5.3
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Weaknesses

CVE ID

CVE-2024-37168

GHSA ID

GHSA-7v5v-9h63-cj86

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.