1586 matches found
Denial Of Service (DoS)
github.com/grpc/grpc-go is vulnerable to denial of service DoS attacks. If an attacker tries to connect a GRPC client to an IP address and port number which has no listeners, the client continues to try and connect to this in an infinite loop. This is because the transportMonitor goroutine does n...
Denial Of Service (DoS)
github.com/andreimatei/grpc-go is vulnerable to denial of service DoS attacks. A malicious user can send an empty hpack string to the system and cause it to crash...
Denial Of Service (DoS)
github.com/grpc/grpc-go is vulnerable to denial of service DoS attacks. A malicious user can send an empty hpack string to the system and cause it to crash...
Denial Of Service (DoS) Via Out-of-Bounds Write
gRPC is vulnerable to Denial of Service DoS attacks. The vulnerability exists due to a heap-based use-after-free UAF issue in the parseunix function. This vulnerability may lead to further attacks...
CVE-2017-8359
Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free related to the grpccalldestroy function in core/lib/surface/call.c...
CVE-2017-8359
Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free related to the grpccalldestroy function in core/lib/surface/call.c...
PYSEC-2017-101
Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free related to the grpccalldestroy function in core/lib/surface/call.c...
DEBIAN-CVE-2017-8359
Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free related to the grpccalldestroy function in core/lib/surface/call.c...
CVE-2017-8359
Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free related to the grpccalldestroy function in core/lib/surface/call.c...
Heap overflow
Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free related to the grpccalldestroy function in core/lib/surface/call.c...
CVE-2017-8359
Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free related to the grpccalldestroy function in core/lib/surface/call.c...
CVE-2017-8359
Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free related to the grpccalldestroy function in core/lib/surface/call.c...
CVE-2017-8359
CVE-2017-8359 affects Google gRPC prior to 2017-03-29, where an out-of-bounds write results from a heap-based use-after-free in the grpc_call_destroy function (core/lib/surface/call.c). The documents identify the root cause and the vulnerable component, but do not specify product versions beyond ...
Google gRPC Heap Buffer Overflow Vulnerability
gRPC is an open source RPC framework . A heap buffer overflow vulnerability exists in the gprfree function within Google gRPC core/lib/support/alloc.c, which allows remote attackers to exploit the vulnerability to submit a special request to execute arbitrary code...
Out-of-Bounds Write
gRPC is vulnerable to an out-of-bounds write. A malicious user can use this to cause a system crash or to overwrite variables currently in the buffer...
Out-of-Bounds Write
gRPC is vulnerable to an out-of-bounds write. A malicious user can use this to cause a system crash or to overwrite variables currently in the buffer. This can be done using the parseunix function in core/ext/clientchannel/parseaddress.c...
grpc: Heap-use-after-free in gpr_unref
Detailed report: https://oss-fuzz.com/testcase?key=6462055064272896 Project: grpc Fuzzer: libFuzzergrpcapifuzzer Fuzz target binary: apifuzzer Job Type: libfuzzerasangrpc Platform Id: linux Crash Type: Heap-use-after-free WRITE 8 Crash Address: 0x611000002340 Crash State: gprunref grpcerrorunref...
CVE-2017-7860
Google gRPC before 2017-02-22 has an out-of-bounds write caused by a heap-based buffer overflow related to the parseunix function in core/ext/clientchannel/parseaddress.c...