First published: Mon Jun 10 2024(Updated: )
@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.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
npm/@grpc/grpc-js | <1.8.22 | 1.8.22 |
npm/@grpc/grpc-js | >=1.9.0<1.9.15 | 1.9.15 |
npm/@grpc/grpc-js | >=1.10.0<1.10.9 | 1.10.9 |
IBM Cloud Pak for Security | <=1.10.0.0 - 1.10.11.0 | |
IBM QRadar Suite Software | <=1.10.12.0 - 1.10.23.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-37168 has a severity rating that indicates it could potentially lead to denial of service due to memory allocation issues.
To remediate CVE-2024-37168, upgrade to versions 1.10.9, 1.9.15, or 1.8.22 of the @grpc/grpc-js package.
CVE-2024-37168 affects the @grpc/grpc-js package versions prior to 1.10.9, 1.9.15, and 1.8.22 as well as certain IBM products.
Exploitation of CVE-2024-37168 can result in excessive memory consumption and potential denial of service.
As of the latest information, there is no evidence to suggest that CVE-2024-37168 is actively being exploited in the wild.