Description
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
Remediation
References
https://github.com/grpc/grpc/pull/32309
https://github.com/grpc/grpc/pull/33005
Related Vulnerabilities
CVE-2022-25892 Vulnerability in npm package hummus
CVE-2016-1000343 Vulnerability in maven package org.bouncycastle:bcprov-jdk15on
CVE-2014-0230 Vulnerability in maven package org.apache.tomcat:catalina
CVE-2017-2604 Vulnerability in maven package org.jenkins-ci.main:jenkins-core
CVE-2022-28220 Vulnerability in maven package org.apache.james:james-server-protocols-managesieve