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-2019-10061 Vulnerability in npm package opencv
CVE-2022-29251 Vulnerability in maven package org.xwiki.platform:xwiki-platform-flamingo-theme-ui
CVE-2022-2596 Vulnerability in maven package org.webjars.npm:node-fetch
CVE-2021-26117 Vulnerability in maven package org.apache.activemq:activemq-jaas
CVE-2023-35152 Vulnerability in maven package org.xwiki.platform:xwiki-platform-like-ui