@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.
References
Configurations
No configuration.
History
11 Jun 2024, 13:54
Type | Values Removed | Values Added |
---|---|---|
Summary |
|
10 Jun 2024, 22:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2024-06-10 22:15
Updated : 2024-06-11 13:54
NVD link : CVE-2024-37168
Mitre link : CVE-2024-37168
CVE.ORG link : CVE-2024-37168
JSON object : View
Products Affected
No product.
CWE
CWE-789
Memory Allocation with Excessive Size Value