chore(deps): bump google.golang.org/grpc to v1.79.3 (CVE)#124
Open
gdrojas wants to merge 1 commit into
Open
Conversation
Fixes Dependabot alert #21: gRPC-Go authorization bypass via missing leading slash in HTTP/2 :path pseudo-header. The vulnerability allowed authorization interceptors (including the official grpc/authz package) to evaluate non-canonical path strings, potentially bypassing "deny" policy rules in setups with a fallback "allow" rule. Severity: CRITICAL on the default branch dependency graph. Changes: - google.golang.org/grpc v1.67.1 -> v1.79.3 (transitive via hashicorp/terraform-plugin-sdk/v2) - go directive 1.23.0 -> 1.24.0 (forced by go mod tidy after the upgrade) - transitive bumps from go mod tidy: golang.org/x/{crypto,mod,net, sync,sys,text,tools}, google.golang.org/{genproto/googleapis/rpc, protobuf}, google/go-cmp Also fixes a pre-existing printf vet violation in null_client.go:331 that the stricter go 1.24 vet now catches: return fmt.Errorf(diag[0].Summary) -> return fmt.Errorf("%s", diag[0].Summary) (non-constant format string in fmt.Errorf — would misinterpret any '%' character in the upstream error message) Build clean, vet clean. The 2 test failures present after this change (TestProvider_HasChildDataSources, TestGenerateParameterValueID) are pre-existing on main and unrelated to this upgrade.
sebastiancorrea81
approved these changes
Jun 1, 2026
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
2 participants
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.
Summary
Fixes Dependabot alert #21 (CRITICAL): gRPC-Go authorization bypass via missing leading slash in
:path.The vulnerability allowed authorization interceptors (including the official
grpc/authzpackage) to evaluate non-canonical:pathstrings, potentially bypassing "deny" policy rules in setups with a fallback "allow" rule.While this provider does not use
grpc/authzdirectly, the transitive dependency is patched as a hygiene measure to clear the Dependabot alert.Changes
Dependency bump
google.golang.org/grpcv1.67.1→v1.79.3(came in transitively viagithub.com/hashicorp/terraform-plugin-sdk/v2 v2.34.0; pinned directly here to override).Collateral (forced by
go mod tidy)godirective:1.23.0→1.24.0golang.org/x/{crypto,mod,net,sync,sys,text,tools},google.golang.org/{genproto/googleapis/rpc,protobuf},google/go-cmpPre-existing lint fix
nullplatform/null_client.go:331had aprintfvet violation that the strictergo 1.24toolchain now flags:The original code would misinterpret any
%character in the upstream error message (e.g., URL-encoded values containing%XXsequences). One-line fix, no behavior change for messages without%.Validation
✅
go buildclean✅
go vet ./...cleango test ./...shows 2 failures — both pre-existing on main, unrelated to this upgrade:TestProvider_HasChildDataSources(expected 6 data sources, found 10)TestGenerateParameterValueID(hash mismatch)Verified by running the same tests against
origin/mainwithout this branch's changes — same 2 failures reproduce. These are tracked separately and should not block this security update.Risk
Low. The dependency upgrade is within a major version line (v1.x), and the changes are confined to transitive deps + one lint fix. No public API of this provider changes.