Repository navigation
chore(deps): update module google.golang.org/grpc to v1.83.2 [security] - #81
renovate[bot] wants to merge 1 commit into
Conversation
[Low risk] The risk rests on a patch-level bump of an indirect gRPC dependency in two modules. The repository has no direct gRPC server use, and the go.sum entries are consistent with the go.mod change. Approved SummaryUpdates indirect gRPC dependencies to v1.83.2 in both Go modules. The columbo and michael module manifests select the patch release, with matching checksum entries added to their go.sum files. Upstream’s v1.83.2 release notes identify a server-side fix rejecting requests missing both :authority and Host headers. The applications’ metrics exporters use OTLP over HTTP, and their source contains no direct gRPC server construction. Review context · 1 source · 1/6 commands
Reviews (1) · Last reviewed commit: "chore(deps): update module google.golang..." · openai/gpt-6.1-sol · $0.05 |
This PR contains the following updates:
v1.83.1→v1.83.2Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
gRPC-Go xDS servers: Denial of Service (DoS) via crash due to missing
:authorityandHostheadersCVE-2026-84445 / GHSA-2v4p-qf9q-27wj
More information
Details
A vulnerability exists in gRPC-Go servers configured with
xds.NewGRPCServer()where a crafted request missing both:authorityandHostheaders can cause a server panic, resulting in a Denial of Service (DoS).Servers built with
xds.NewGRPCServerinstall an xDS routing interceptor on every RPC. This interceptor looks up the request’s:authorityheader to pick a virtual host. The HTTP/2 server transport previously accepted requests that had neither:authoritynorHost. When this happened, the xDS routing interceptor attempted to access the first element of an empty slice of authorities, leading to an index out of bounds panic. Since the per-RPC goroutine does not recover from panics, the entire server process would terminate.This panic occurs in the interceptor pipeline, meaning the transport credentials handshake (TLS, mTLS, or ALTS) and HTTP/2 connection establishment must complete successfully before the crafted request can reach this logic.
Impact
An attacker can cause a complete outage of the gRPC server by sending a request missing both
:authorityandHostheaders, provided they can successfully establish a transport connection.Patches
The issue has been addressed in
master(and backported to1.84.0,1.83.2and1.82.2). The fix updates the HTTP/2 transport layer to reject requests missing both:authorityandHostheaders early, maintaining consistency with and other gRPC language implementations.Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
grpc/grpc-go (google.golang.org/grpc)
v1.83.2: Release 1.83.2Compare Source
Security
:authorityandHostheaders with HTTP 400 and statusInternal. (#9365)Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.