Vulnerabilities

@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon.

@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon.

@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon.

gRPC-Go is the Go language implementation of gRPC.

gRPC-Go is the Go language implementation of gRPC.

gRPC-Go is the Go language implementation of gRPC.

@grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon.

@grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon.

gRPC-Go is the Go language implementation of gRPC.

There exists a denial of service through Data corruption in gRPC-C++ - gRPC-C++ servers with transmit zero copy enabled through the channel arg GRPC_ARG_TCP_TX_ZEROCOPY_ENABLED can experience data corruption issues.

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.

@grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon.

The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

Lack of error handling in the TCP server in Google's gRPC starting version 1.23 on posix-compatible platforms (ex.

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:…

When gRPC HTTP2 stack raised a header size exceeded error, it skipped parsing the rest of the HPACK frame.

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…

There exists an vulnerability causing an abort() to be called in gRPC.

grpc-swift is the Swift language implementation of gRPC, a remote procedure call (RPC) framework.

The package grpc before 1.24.4; the package @grpc/grpc-js before 1.1.8 are vulnerable to Prototype Pollution via loadPackageDefinition.

Google gRPC before 2017-04-05 has an out-of-bounds write caused by a heap-based buffer overflow related to core/lib/iomgr/error.c.

Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free related to the grpc_call_destroy function in core/lib/surface/call.c.

Google gRPC before 2017-02-22 has an out-of-bounds write related to the gpr_free function in core/lib/support/alloc.c.

Google gRPC before 2017-02-22 has an out-of-bounds write caused by a heap-based buffer overflow related to the parse_unix function in core/ext/client_channel/parse_address.c.