Update dependency @grpc/grpc-js to v1.9.15 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@grpc/grpc-js (source)	1.9.1 -> 1.9.15

GitHub Vulnerability Alerts

CVE-2024-37168

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

---

Release Notes

grpc/grpc-node (@​grpc/grpc-js)

v1.9.15: @​grpc/grpc-js 1.9.15

Compare Source

• Avoid buffering significantly more than grpc.max_receive_message_size per received message.

v1.9.14: @​grpc/grpc-js 1.9.14

Compare Source

• Fix a bug that could rarely cause connection leaks (#​2644)
• Fix a bug that could cause clients to go IDLE incorrectly some time after calling waitForReady (#​2643)

v1.9.13: @​grpc/grpc-js 1.9.13

Compare Source

• Fix a bug that could cause the Node process to close early when establishing a connection while a request is pending (#​2626)

v1.9.12: @​grpc/grpc-js 1.9.12

Compare Source

• Fix a bug that could cause connectivity state information to become stale in some circumstances (#​2623)

v1.9.11: @​grpc/grpc-js 1.9.11

Compare Source

• Fix a busy loop when recovering from a failure to establish a connection to a unix domain socket address target (#​2618)
• Fix a bug that caused clients to stop trying to connect to a fixed IP address target after a working connection drops (#​2619)

v1.9.10: @​grpc/grpc-js 1.9.10

Compare Source

• Provide the correct port to the proxy when connecting to a target without an explicitly specified port (#​2608 contributed by @​segevfiner)
• Properly handle goaway events with no additional data attached (#​2611)

v1.9.9

Compare Source

v1.9.8

Compare Source

v1.9.7: @​grpc/grpc-js 1.9.7

Compare Source

• Fix a bug that could cause a client to not update name resolution after multiple failed connection attempts (#​2602)

v1.9.6: @​grpc/grpc-js 1.9.6

Compare Source

• Include more information in most "No connection established" errors (#​2598)
• Remove the index tracer, and add more information to other trace logs (#​2599)

v1.9.5: @​grpc/grpc-js 1.9.5

Compare Source

• Fix a type inconsistency in server-call.ts (#​2589 contributed by @​rsnullptr)
• Close ports if the server is shut down while the bind operation is ongoing (#​2590)

v1.9.4: @​grpc/grpc-js 1.9.4

Compare Source

• Fix a bug that could cause a client to sometimes incorrectly hold the process open when no longer in use (#​2586)

v1.9.3: @​grpc/grpc-js 1.9.3

Compare Source

• Make a few improvements to DNS resolving timing (#​2571)

Experimental changes:

• Added grpc.experimental.BackoffTimeout#getEndTime

v1.9.2: @​grpc/grpc-js 1.9.2

Compare Source

• Handle error when sending keepalive pings (#​2563)
• Fix a bug that could cause invalid connection states when DNS updates contained the same address the client was already connected to (#​2559 contributed by @​gusumuzhe, backported in #​2564)

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 50cd76c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[google-oss-bot]

Size Report ¹

Affected Products

• @firebase/firestore

  Type	Base (a90255a)	Merge (29a1421)	Diff
  main	582 kB	582 kB	+1 B (+0.0%)

Test Logs

• Base (a90255a): https://github.com/firebase/firebase-js-sdk/actions/runs/9391103140
• Merge (29a1421): https://github.com/firebase/firebase-js-sdk/actions/runs/9458159699

1. https://storage.googleapis.com/firebase-sdk-metric-reports/gL2XpDSKW2.html

[google-oss-bot]

Size Analysis Report ¹

Affected Products

No changes between base commit (a90255a) and merge commit (29a1421).

Test Logs

• Base (a90255a): https://github.com/firebase/firebase-js-sdk/actions/runs/9391103140
• Merge (29a1421): https://github.com/firebase/firebase-js-sdk/actions/runs/9458159699

1. https://storage.googleapis.com/firebase-sdk-metric-reports/SzJBsc8fuY.html