grpc 1.33.0.pre1
Connection confusion in gRPC
high severity CVE-2023-32731>= 1.53.1
When gRPC HTTP2 stack raised a header size exceeded error, it skipped parsing the rest of the HPACK frame. This caused any HPACK table mutations to also be skipped, resulting in a desynchronization of HPACK tables between sender and receiver. If leveraged, say, between a proxy and a backend, this could lead to requests from the proxy being interpreted as containing headers from different proxy clients
- leading to an information leak that can be used for privilege escalation or data exfiltration. We recommend upgrading beyond the commit contained in https://github.com/grpc/grpc/pull/32309
gRPC Reachable Assertion issue
high severity CVE-2023-1428>= 1.53.0
There exists an vulnerability causing an abort() to be called in gRPC. The following headers cause gRPC's C++ implementation to abort() when called via http2:
te: x (x != trailers)
:scheme: x (x != http, https)
grpclb_client_stats: x (x == anything)
On top of sending one of those headers, a later header must be sent that gets the total header size past 8KB. We recommend upgrading past git commit 2485fa94bd8a723e5c977d55a3ce10b301b437f8 or v1.53 and above.
gRPC connection termination issue
medium severity CVE-2023-32732>= 1.53.0
gRPC contains a vulnerability whereby a client can cause a
termination of connection between a HTTP2 proxy and a gRPC server:
a base64 encoding error for -bin suffixed headers will result in
a disconnection by the gRPC server, but is typically allowed by
HTTP2 proxies. We recommend upgrading beyond the commit in
https://github.com/grpc/grpc/pull/32309.
No officially reported memory leakage issues detected.
This gem version does not have any officially reported memory leaked issues.
No license issues detected.
This gem version has a license in the gemspec.
This gem version is available.
This gem version has not been yanked and is still available for usage.