🚨 [security] Update @restorecommerce/rc-grpc-clients 5.1.30 → 5.1.32 (patch)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​restorecommerce/rc-grpc-clients (5.1.30 → 5.1.32) · Repo · Changelog

Release Notes

5.1.32 (from changelog)

Note: Version bump only for package @restorecommerce/rc-grpc-clients

Does any of this look wrong? Please let us know.

✳️ @​restorecommerce/grpc-client (2.2.2 → 2.2.4) · Repo · Changelog

Release Notes

2.2.4 (from changelog)

Note: Version bump only for package @restorecommerce/grpc-client

Does any of this look wrong? Please let us know.

✳️ @​restorecommerce/logger (1.2.11 → 1.3.1) · Repo · Changelog

Release Notes

1.3.1 (from changelog)

Bug Fixes

• logger: Defaulting of stringifyMeta option (28b92f3)

Does any of this look wrong? Please let us know.

↗️ @​grpc/grpc-js (indirect, 1.10.8 → 1.10.10) · Repo

Security Advisories 🚨

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

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

Sorry, we couldn't find anything useful about this release.

↗️ protobufjs (indirect, 7.3.0 → 7.3.2) · Repo · Changelog

Release Notes

7.3.2 (from changelog)

Bug Fixes

• docs: Update readme to correct command for creating types (#1939) (0f9d477)

7.3.1 (from changelog)

Bug Fixes

• types: reserved field in IType can contain reserved names (#2001) (d1d2c0c)

Does any of this look wrong? Please let us know.

🆕 uuid (added, 10.0.0)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[coveralls]

Pull Request Test Coverage Report for Build 9703942386

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 86.335%

---

Totals
Change from base Build 9427921305:	0.0%
Covered Lines:	355
Relevant Lines:	408

---

💛 - Coveralls

[depfu]

Closed in favor of #32.