cve,link,title,description,vendor,products,score,severity,epss,cisa,article,ransomware,exploited,poc,trended,trended_no_1,published,trended_score
CVE-2024-7246,https://securityvulnerability.io/vulnerability/CVE-2024-7246,gRPC vulnerability allows client-side scripting and HTTP header leakage,"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.",Google,Grpc,,,0.0004299999854993075,false,false,false,false,,false,false,2024-08-06T10:14:28.492Z,0
CVE-2023-4785,https://securityvulnerability.io/vulnerability/CVE-2023-4785,"Denial of Service in gRPC Core ","Lack of error handling in the TCP server in Google's gRPC starting version 1.23 on posix-compatible platforms (ex. Linux) allows an attacker to cause a denial of service by initiating a significant number of connections with the server. Note that gRPC C++ Python, and Ruby are affected, but gRPC Java, and Go are NOT affected. ",Google,gRPC,7.5,HIGH,0.0010900000343099236,false,false,false,false,,false,false,2023-09-13T17:15:00.000Z,0
CVE-2023-33953,https://securityvulnerability.io/vulnerability/CVE-2023-33953,Denial-of-Service in gRPC,"gRPC contains a vulnerability that allows hpack table accounting errors could lead to unwanted disconnects between clients and servers in exceptional cases/ Three vectors were found that allow the following DOS attacks:

- Unbounded memory buffering in the HPACK parser
- Unbounded CPU consumption in the HPACK parser

The unbounded CPU consumption is down to a copy that occurred per-input-block in the parser, and because that could be unbounded due to the memory copy bug we end up with an O(n^2) parsing loop, with n selected by the client.

The unbounded memory buffering bugs:

- The header size limit check was behind the string reading code, so we needed to first buffer up to a 4 gigabyte string before rejecting it as longer than 8 or 16kb.
- HPACK varints have an encoding quirk whereby an infinite number of 0’s can be added at the start of an integer. gRPC’s hpack parser needed to read all of them before concluding a parse.
- gRPC’s metadata overflow check was performed per frame, so that the following sequence of frames could cause infinite buffering: HEADERS: containing a: 1 CONTINUATION: containing a: 2 CONTINUATION: containing a: 3 etc…",Google,Grpc,7.5,HIGH,0.000750000006519258,false,false,false,false,,false,false,2023-08-09T13:15:00.000Z,0
CVE-2023-1428,https://securityvulnerability.io/vulnerability/CVE-2023-1428,Denial-of-Service in gRPC,"There exists an vulnerability causing an abort() to be called in gRPC. 
The following headers cause gRPC's C++ implementation to abort() when called via http2:

te: x (x != trailers)

:scheme: x (x != http, https)

grpclb_client_stats: x (x == anything)

On top of sending one of those headers, a later header must be sent that gets the total header size past 8KB. We recommend upgrading past git commit 2485fa94bd8a723e5c977d55a3ce10b301b437f8 or v1.53 and above.

",Google,Grpc,7.5,HIGH,0.0012700000079348683,false,false,false,false,,false,false,2023-06-09T11:15:00.000Z,0
CVE-2023-32731,https://securityvulnerability.io/vulnerability/CVE-2023-32731,Information leak 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. We recommend upgrading beyond the commit contained in  https://github.com/grpc/grpc/pull/33005 https://github.com/grpc/grpc/pull/33005 
",Google,Grpc,7.4,HIGH,0.001610000035725534,false,false,false,false,,false,false,2023-06-09T11:15:00.000Z,0
CVE-2023-32732,https://securityvulnerability.io/vulnerability/CVE-2023-32732,Denial-of-Service in gRPC,"gRPC contains a vulnerability whereby a client can cause a termination of connection between a HTTP2 proxy and a gRPC server: a base64 encoding error for `-bin` suffixed headers will result in a disconnection by the gRPC server, but is typically allowed by HTTP2 proxies. We recommend upgrading beyond the commit in  https://github.com/grpc/grpc/pull/32309 https://www.google.com/url 
",Google,Grpc,5.3,MEDIUM,0.0007699999841861427,false,false,false,false,,false,false,2023-06-09T11:15:00.000Z,0