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
{
"cna_assigner": "Google",
"cwe_ids": [
"CWE-440"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/32xxx/CVE-2023-32731.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "1.53"
},
{
"last_affected": "1.54"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"cpe": "cpe:2.3:a:grpc:grpc:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "1.53.0"
},
{
"fixed": "1.55.0"
}
],
"source": "CPE_RANGE"
}
]
}