gRPC up to 1.65.3 HTTP/2 not expected behavior violation

Summaryinfo

A vulnerability classified as problematic has been found in gRPC. This affects an unknown function of the component HTTP2 Handler. Performing a manipulation of the argument not results in expected behavior violation. This vulnerability is cataloged as CVE-2024-7246. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in gRPC. This affects some unknown processing of the component HTTP2 Handler. The manipulation of the argument not with an unknown input leads to a expected behavior violation vulnerability. CWE is classifying the issue as CWE-440. A feature, API, or function does not perform according to its specification. This is going to have an impact on availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2024-7246 since 07/29/2024. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 210402 (RHEL 8 / 9 : Satellite 6.16.0 (Critical) (RHSA-2024:8906)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.58.3, 1.59.5, 1.60.2, 1.61.3, 1.62.3, 1.63.2, 1.64.3 or 1.65.4 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (210402). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• gRPC

Version

• 1.53.0
• 1.53.1
• 1.53.2
• 1.54.0
• 1.54.1
• 1.54.3
• 1.55.0
• 1.55.1
• 1.55.3
• 1.55.4
• 1.56.0
• 1.56.1
• 1.56.2
• 1.56.3
• 1.56.4
• 1.57.0
• 1.57.1
• 1.58.0
• 1.58.1
• 1.58.2
• 1.59.0
• 1.59.1
• 1.59.2
• 1.59.3
• 1.59.4
• 1.60.0
• 1.60.1
• 1.61.0
• 1.61.1
• 1.61.2
• 1.62.0
• 1.62.1
• 1.62.2
• 1.63.0
• 1.63.1
• 1.64.0
• 1.64.1
• 1.64.2
• 1.65.0
• 1.65.1
• 1.65.2
• 1.65.3

Website

• Product: https://github.com/grpc/grpc/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion