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-2021-4040 Vulnerability in maven package org.apache.activemq:artemis-commons
CVE-2021-27191 Vulnerability in npm package get-ip-range
CVE-2018-14042 Vulnerability in maven package org.webjars.npm:bootstrap
CVE-2020-36649 Vulnerability in maven package org.webjars.bowergithub.mholt:papaparse
CVE-2020-7769 Vulnerability in maven package org.webjars.npm:nodemailer