| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in grpc. It has been rated as problematic. The impacted element is an unknown function of the component HTTP2 Stack. The manipulation leads to expected behavior violation. This vulnerability is documented as CVE-2023-32731. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in grpc (version unknown) and classified as problematic. This issue affects an unknown function of the component HTTP2 Stack. The manipulation with an unknown input leads to a expected behavior violation vulnerability. Using CWE to declare the problem leads to CWE-440. A feature, API, or function does not perform according to its specification. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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/32309 https://github.com/grpc/grpc/pull/32309
The weakness was released 06/09/2023. The advisory is shared at github.com. The identification of this vulnerability is CVE-2023-32731 since 05/12/2023. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 212043 (RHEL 9 : rhc-worker-playbook (RHSA-2024:10761)), which helps to determine the existence of the flaw in a target environment.
Upgrading eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at Tenable (212043). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Website
- Product: https://github.com/grpc/grpc/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 7.4
CNA Vector (Google Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Expected behavior violationCWE: CWE-440 / CWE-436
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 212043
Nessus Name: RHEL 9 : rhc-worker-playbook (RHSA-2024:10761)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
05/12/2023 🔍06/09/2023 🔍
06/09/2023 🔍
12/04/2024 🔍
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2023-32731 (🔍)
GCVE (CVE): GCVE-0-2023-32731
GCVE (VulDB): GCVE-100-231161
Entry
Created: 06/09/2023 14:27Updated: 12/04/2024 06:02
Changes: 06/09/2023 14:27 (47), 07/07/2023 18:06 (11), 12/04/2024 06:02 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.