HPACK table poisoning in gRPC C++, Python & Ruby
Google gRPC
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Google gRPC |
| No fix yet |
Original description
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.