It's possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy and the backend such that other clients see failed requests. It's also possible to use this vulnerability to leak other clients HTTP header keys, but not values. This occurs because the error status for a misencoded header is not cleared between header reads, resulting in subsequent (incrementally indexed) added headers in the first request being poisoned until cleared from the HPACK table. Please update to a fixed version of gRPC as soon as possible. This bug has been fixed in 1.58.3, 1.59.5, 1.60.2, 1.61.3, 1.62.3, 1.63.2, 1.64.3, 1.65.4.
AI analysis not yet available
Plain-English explanation, risk summary, and remediation steps will appear here once AI analysis is complete.
No Fix Known
No patch has been released yet. Apply workarounds or mitigations where available.
Published
CVE disclosed publicly
Last Modified
Most recent update
Indexed to CVEInsight
Added to this platform
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
8
Affected Products
1
References
grpc / grpc
| grpc | grpc | 1.60.0 - 1.60.2 | - |
| grpc | grpc | 1.61.0 - 1.61.3 | - |
| grpc | grpc | 1.62.0 - 1.62.3 | - |
| grpc | grpc | 1.63.0 - 1.63.2 | - |
| grpc | grpc | 1.64.0 - 1.64.3 | - |
| grpc | grpc | 1.65.0 - 1.65.4 | - |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Exploitability
Impact