Aller au contenu
en Se connecter
7.4 Élevée

CVE-2023-32731 When gRPC HTTP2 stack raised a header size exceeded error, it skipped parsing the rest of the HPACK frame

Description

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

Produits et versions touchés

Produit Versions touchées Corrigé en
gRPC 1.53 1.53 → 1.54 Pas de correctif indiqué
grpc 1.53 1.53 → 1.54 Pas de correctif indiqué

Références

Chronologie

  1. Publiée
  2. Dernière modification

Autres CVE de gRPC

Les 6 CVE de gRPC →
CVE-2024-7246 It's possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy and the… 6.3 Moyenne CVE-2023-4785 Lack of error handling in the TCP server in Google's gRPC starting version 1.23 on posix-compatible platforms (ex 7.5 Élevée CVE-2023-33953 gRPC contains a vulnerability that allows hpack table accounting errors could lead to unwanted disconnects between… 7.5 Élevée CVE-2023-32732 gRPC contains a vulnerability whereby a client can cause a termination of connection between a HTTP2 proxy and a gRPC… 5.3 Moyenne
Suivre cette CVE