NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2024-37168: @grpc/grpc-js can allocate memory for incoming messages well above configured limits

mediumCVSS 3.1 5.3GHSA-7v5v-9h63-cj86

Impact There are two separate code paths in which memory can be allocated per message in excess of the grpc.maxreceivemessagelength 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.

Published Jun 10, 2024 · Updated Jun 11, 2024

Affected packages

@grpc/grpc-js

Ecosystem
npm
Affected
>= 1.10.0, < 1.10.9
Fixed in
1.10.9
Check
npm ls @grpc/grpc-js

@grpc/grpc-js

Ecosystem
npm
Affected
>= 1.9.0, < 1.9.15
Fixed in
1.9.15
Check
npm ls @grpc/grpc-js

@grpc/grpc-js

Ecosystem
npm
Affected
< 1.8.22
Fixed in
1.8.22
Check
npm ls @grpc/grpc-js

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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

Credited to jhump.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries