Repository navigation
chore(deps): update dependency @grpc/grpc-js to v1.14.5 [security] - #210
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.14.4→1.14.5@grpc/grpc-js: In certain configurations, getAuthContext can return unauthorized certificates as though they were authorized
CVE-2026-101916 / GHSA-m9gg-hp2v-232j
More information
Details
Impact
When server credentials are created with the
requireClientCertificateoption set tofalse,getAuthContextdoes not distinguish between authorized and unauthorized certificates in its return value. This can create improper authentication vulnerabilities for@grpc/grpc-jsusers who use the result ofgetAuthContextfor authentication.In particular,
@grpc/grpc-js-xdscan both set therequireClientCertificateoption tofalseand use the return value ofgetAuthContextfor RBAC authentication in some configurations.Patches
This vulenrability is fixed in 1.13.6 and 1.14.5.
Workarounds
@grpc/grpc-jsusers usinggetAuthContextthis way can avoid this problem by settingrequireClientCertificatetotrue.@grpc/grpc-js-xdsusers using RBAC can avoid this by setting therequire_client_certificatefield totruein the DownstreamTlsContext in the xDS configuration.Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
@grpc/grpc-js: The server transmits some error messages thrown by method handlers to the client in status messages
CVE-2026-101915 / GHSA-f596-whhp-79r4
More information
Details
Impact
If an application method handler crashes, the error message is included in the status message sent to the client. This can leak to the client any sensitive data that may be included in the error message. This impacts anyone using
@grpc/grpc-jsto run servers.Patches
This vulnerability is fixed in 1.13.6 and 1.14.5.
Workarounds
This can be avoided by using a top-level error handler in method handlers to strip out sensitive error information.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
grpc/grpc-node (@grpc/grpc-js)
v1.14.5: @grpc/grpc-js 1.14.5Compare Source
getAuthContextto return unverified certificates as though they were verified in some configurations (advisory GHSA-m9gg-hp2v-232j)Configuration
📅 Schedule: (in timezone Asia/Singapore)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.