First published: Tue Jun 13 2023(Updated: )
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 <a href="https://github.com/grpc/grpc/pull/32309">https://github.com/grpc/grpc/pull/32309</a> <a href="https://github.com/grpc/grpc/pull/32309">https://github.com/grpc/grpc/pull/32309</a>
Affected Software | Affected Version | How to fix |
---|---|---|
gRPC | <commit 32309 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2214463 is medium due to potential desynchronization issues affecting data integrity between gRPC endpoints.
To fix REDHAT-BUG-2214463, update to a version of gRPC that includes the patch for the header size exceeded error.
REDHAT-BUG-2214463 affects versions of gRPC up to commit 32309.
Systems using gRPC for communication, particularly those with proxy and backend configurations, are impacted by REDHAT-BUG-2214463.
REDHAT-BUG-2214463 describes a desynchronization of HPACK tables due to skipped parsing of HPACK frames when a header size exceeded error occurs.