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.
{
    "nvd_published_at": "2023-06-09T11:15:09Z",
    "severity": "HIGH",
    "github_reviewed": true,
    "github_reviewed_at": "2023-07-05T20:26:48Z",
    "cwe_ids": [
        "CWE-440"
    ]
}