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-25031 Vulnerability in maven package org.webjars.npm:swagger-ui-dist
CVE-2020-9298 Vulnerability in maven package com.netflix.spinnaker.orca:orca-core
CVE-2023-29515 Vulnerability in maven package org.xwiki.platform:xwiki-platform-appwithinminutes-ui
CVE-2016-8738 Vulnerability in maven package org.apache.struts:struts2-core
CVE-2020-35217 Vulnerability in maven package io.vertx:vertx-web