Advisory

GHSA-7v5v-9h63-cj86

Also known as: CVE-2024-37168

Summary

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

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-06-10 21:38 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

@grpc/grpc-js

npm · All systems

Affected

  • introduced 1.10.0, fixed 1.10.9 (semver)

Fixed versions

1.10.9

Fix

@grpc/grpc-js

npm · All systems

Affected

  • introduced 1.9.0, fixed 1.9.15 (semver)

Fixed versions

1.9.15

Fix

@grpc/grpc-js

npm · All systems

Affected

  • introduced 0, fixed 1.8.22 (semver)

Fixed versions

1.8.22

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences