CVE-2023-32731 — Expected Behavior Violation in Grpc

Vendor	Product	Version range	Fixed in
debian	grpc	—	—
google	grpc	1.53 – 1.54	—
grpc	grpc	>= 1.53.0 < 1.55.0	1.55.0
grpc	grpc	>= 1.53.0 < 1.53.1	1.53.1
grpc	grpc	>= 1.54.0 < 1.54.2	1.54.2
msrc	azl3_grpc_1.42.0-7_on_azure_linux_3.0	—	—
msrc	azl3_python-tensorboard_2.16.2-6_on_azure_linux_3.0	—	—
msrc	azure_linux_3.0_arm	—	—
msrc	azure_linux_3.0_x64	—	—

Microsoft

Information leak in gRPC

vendor_msrc·2023-06-13·CVSS 7.4

CVE-2023-32731 [HIGH] CWE-440 Information leak in gRPC Information leak in gRPC FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability? One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this. Mariner: Mariner Google: Google Customer Action Required: Yes Remediation: CBL-Mariner Releases Reference: https://learn.microsoft.com/en-us/azure/az

Red Hat

gRPC: sensitive information disclosure

vendor_redhat·2023-06-09·CVSS 7.4

CVE-2023-32731 [HIGH] CWE-440 gRPC: sensitive information disclosure gRPC: sensitive information disclosure 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 A flaw was found in gRPC. This flaw allows a remote attacker to obtain sensitive information, caused by a flaw when the gRP

Debian

CVE-2023-32731: grpc - When gRPC HTTP2 stack raised a header size exceeded error, it skipped parsing th...

vendor_debian·2023·CVSS 7.4

CVE-2023-32731 [HIGH] CVE-2023-32731: grpc - When gRPC HTTP2 stack raised a header size exceeded error, it skipped parsing th... 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 Scope: local bookworm: resolved bullseye: resolved forky: resolved sid: resolved trixie: resolved

OSV

Connection confusion in gRPC

osv·2023-07-05

CVE-2023-32731 [HIGH] Connection confusion in gRPC Connection confusion in gRPC 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.

GHSA

Connection confusion in gRPC

ghsa·2023-07-05

CVE-2023-32731 [HIGH] CWE-440 Connection confusion in gRPC Connection confusion in gRPC 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.

OSV

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

osv·2023-06-09·CVSS 7.5

CVE-2023-32731 [HIGH] CVE-2023-32731: When gRPC HTTP2 stack raised a header size exceeded error, it skipped parsing the rest of the HPACK frame 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

CVE-2023-32731: 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…

Affected

CVSS provenance