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/33005 https://github.com/grpc/grpc/pull/33005
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:HGrpc
APPGrpc1.53.0 – 1.55.0 (bez)
Related vulnerabilities
gRPC-Go: Authorization Bypass przez nieprawidłowy nagłówek HTTP/2 :path
Google gRPC before 2017-04-05 has an out-of-bounds write caused by a heap-based buffer overflow related to cor...
Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free related to the ...
Google gRPC before 2017-02-22 has an out-of-bounds write related to the gpr_free function in core/lib/support/...
Google gRPC before 2017-02-22 has an out-of-bounds write caused by a heap-based buffer overflow related to the...