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-2018-9206 Vulnerability in maven package org.webjars.npm:blueimp-file-upload
CVE-2021-23348 Vulnerability in npm package portprocesses
CVE-2021-4245 Vulnerability in npm package rfc6902
CVE-2021-21369 Vulnerability in maven package org.hyperledger.besu:plugin-api
CVE-2017-5645 Vulnerability in maven package org.apache.logging.log4j:log4j