fix(deps): update module google.golang.org/grpc to v1.56.3 [security] - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
google.golang.org/grpc	v1.53.0 -> v1.56.3

GitHub Vulnerability Alerts

GHSA-m425-mq94-257g

Impact

In affected releases of gRPC-Go, it is possible for an attacker to send HTTP/2 requests, cancel them, and send subsequent requests, which is valid by the HTTP/2 protocol, but would cause the gRPC-Go server to launch more concurrent method handlers than the configured maximum stream limit.

Patches

This vulnerability was addressed by #​6703 and has been included in patch releases: 1.56.3, 1.57.1, 1.58.3. It is also included in the latest release, 1.59.0.

Along with applying the patch, users should also ensure they are using the grpc.MaxConcurrentStreams server option to apply a limit to the server's resources used for any single connection.

Workarounds

None.

References

#​6703

CVE-2023-44487

HTTP/2 Rapid reset attack

The HTTP/2 protocol allows clients to indicate to the server that a previous stream should be canceled by sending a RST_STREAM frame. The protocol does not require the client and server to coordinate the cancellation in any way, the client may do it unilaterally. The client may also assume that the cancellation will take effect immediately when the server receives the RST_STREAM frame, before any other data from that TCP connection is processed.

Abuse of this feature is called a Rapid Reset attack because it relies on the ability for an endpoint to send a RST_STREAM frame immediately after sending a request frame, which makes the other endpoint start working and then rapidly resets the request. The request is canceled, but leaves the HTTP/2 connection open.

The HTTP/2 Rapid Reset attack built on this capability is simple: The client opens a large number of streams at once as in the standard HTTP/2 attack, but rather than waiting for a response to each request stream from the server or proxy, the client cancels each request immediately.

The ability to reset streams immediately allows each connection to have an indefinite number of requests in flight. By explicitly canceling the requests, the attacker never exceeds the limit on the number of concurrent open streams. The number of in-flight requests is no longer dependent on the round-trip time (RTT), but only on the available network bandwidth.

In a typical HTTP/2 server implementation, the server will still have to do significant amounts of work for canceled requests, such as allocating new stream data structures, parsing the query and doing header decompression, and mapping the URL to a resource. For reverse proxy implementations, the request may be proxied to the backend server before the RST_STREAM frame is processed. The client on the other hand paid almost no costs for sending the requests. This creates an exploitable cost asymmetry between the server and the client.

Multiple software artifacts implementing HTTP/2 are affected. This advisory was originally ingested from the swift-nio-http2 repo advisory and their original conent follows.

swift-nio-http2 specific advisory

swift-nio-http2 is vulnerable to a denial-of-service vulnerability in which a malicious client can create and then reset a large number of HTTP/2 streams in a short period of time. This causes swift-nio-http2 to commit to a large amount of expensive work which it then throws away, including creating entirely new Channels to serve the traffic. This can easily overwhelm an EventLoop and prevent it from making forward progress.

swift-nio-http2 1.28 contains a remediation for this issue that applies reset counter using a sliding window. This constrains the number of stream resets that may occur in a given window of time. Clients violating this limit will have their connections torn down. This allows clients to continue to cancel streams for legitimate reasons, while constraining malicious actors.

---

Release Notes

grpc/grpc-go (google.golang.org/grpc)

v1.56.3: Release 1.56.3

Compare Source

Security

• server: prohibit more than MaxConcurrentStreams handlers from running at once (CVE-2023-44487)

  In addition to this change, applications should ensure they do not leave running tasks behind related to the RPC before returning from method handlers, or should enforce appropriate limits on any such work.

v1.56.2: Release 1.56.2

Compare Source

• status: To fix a panic, status.FromError now returns an error with codes.Unknown when the error implements the GRPCStatus() method, and calling GRPCStatus() returns nil. (#​6374)

v1.56.1: Release 1.56.1

Compare Source

• client: handle empty address lists correctly in addrConn.updateAddrs

v1.56.0: Release 1.56.0

Compare Source

New Features

• client: support channel idleness using WithIdleTimeout dial option (#​6263)
  • This feature is currently disabled by default, but will be enabled with a 30 minute default in the future.
• client: when using pickfirst, keep channel state in TRANSIENT_FAILURE until it becomes READY (gRFC A62) (#​6306)
• xds: Add support for Custom LB Policies (gRFC A52) (#​6224)
• xds: support pick_first Custom LB policy (gRFC A62) (#​6314) (#​6317)
• client: add support for pickfirst address shuffling (gRFC A62) (#​6311)
• xds: Add support for String Matcher Header Matcher in RDS (#​6313)
• xds/outlierdetection: Add Channelz Logger to Outlier Detection LB (#​6145)
  • Special Thanks: @​s-matyukevich
• xds: enable RLS in xDS by default (#​6343)
• orca: add support for application_utilization field and missing range checks on several metrics setters
• balancer/weightedroundrobin: add new LB policy for balancing between backends based on their load reports (gRFC A58) (#​6241)
• authz: add conversion of json to RBAC Audit Logging config (#​6192)
• authz: add support for stdout logger (#​6230 and #​6298)
• authz: support customizable audit functionality for authorization policy (#​6192 #​6230 #​6298 #​6158 #​6304 and #​6225)

Bug Fixes

• orca: fix a race at startup of out-of-band metric subscriptions that would cause the report interval to request 0 (#​6245)
• xds/xdsresource: Fix Outlier Detection Config Handling and correctly set xDS Defaults (#​6361)
• xds/outlierdetection: Fix Outlier Detection Config Handling by setting defaults in ParseConfig() (#​6361)

API Changes

• orca: allow a ServerMetricsProvider to be passed to the ORCA service and ServerOption (#​6223)

v1.55.1: Release 1.55.1

Compare Source

• status: To fix a panic, status.FromError now returns an error with codes.Unknown when the error implements the GRPCStatus() method, and calling GRPCStatus() returns nil. (#​6374)

v1.55.0: Release 1.55.0

Compare Source

Behavior Changes

• xds: enable federation support by default (#​6151)
• status: status.Code and status.FromError handle wrapped errors (#​6031 and #​6150)
  • Special Thanks: @​psyhatter

New Features

• xds/xdsclient: support ignore_resource_deletion server feature as per gRFC A53 (#​6035)
• security/advancedtls: add min/max TLS version selection options (#​6007)
  • Special Thanks: @​joeljeske

Bug Fixes

• xds: stop routing RPCs to deleted clusters (#​6125)
• client: fix race between stream creation and GOAWAY receipt, which could lead to spurious UNAVAILABLE stream errors (#​6142)

Performance Improvements

• server: improve stream handler goroutine worker allocation when NumStreamWorkers is used (#​6004)
  • Special Thanks: @​SaveTheRbtz

v1.54.1: Release 1.54.1

Compare Source

Bug Fixes

• credentials/alts: revert a change that causes a crash in the handshaker

v1.54.0: Release 1.54.0

Compare Source

Behavior Changes

• xds: remove support for xDS v2 transport API (#​6013)

New Features

• server: expose SetSendCompressor API to set send compressor name (#​5744)
  • Special Thanks: @​jronak
• xdsclient: include Node proto only in the first discovery request message, to improve performance (#​6078)

Bug Fixes

• metadata: fix validation logic and properly validate metadata appended via AppendToOutgoingContext (#​6001)
  • Special Thanks: @​ktalg
• transport: do not close connections when we encounter I/O errors until after all data is consumed (#​6110)
• ringhash: ensure addresses are consistently hashed across updates (#​6066)
• xds/clusterimpl: fix a bug causing unnecessary closing and re-opening of LRS streams (#​6112)
• xds: NACK route configuration if sum of weights of weighted clusters exceeds uint32_max (#​6085)

Documentation

• resolver: update Resolver.Scheme() docstring to mention requirement of lowercase scheme names (#​6014)
• resolver: document expected error handling of UpdateState errors (#​6002)
  • Special Thanks: @​fho
• examples: add example for ORCA load reporting (#​6114)
• examples: add an example to illustrate authorization (authz) support (#​5920)
  • Special Thanks: @​KenxinKun

---

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 was generated by Mend Renovate. View the repository job log.