1275 matches found
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 ...
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...
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
Project: https://github.com/grpc/grpc.git 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:...
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...
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...
Design/Logic Flaw
Google gRPC before 2017-02-22 has an out-of-bounds write related to the gprfree function in core/lib/support/alloc.c...
CVE-2017-7861
Google gRPC before 2017-02-22 has an out-of-bounds write related to the gprfree function in core/lib/support/alloc.c...
Heap overflow
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...
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...
CVE-2017-7861
Google gRPC before 2017-02-22 has an out-of-bounds write related to the gprfree function in core/lib/support/alloc.c...
CVE-2017-7861
Google gRPC before 2017-02-22 has an out-of-bounds write related to the gprfree function in core/lib/support/alloc.c...
CVE-2017-7860
CVE-2017-7860 : Google gRPC before 2017-02-22 has an out-of-bounds write caused by a heap-based buffer overflow in parse_unix (core/ext/client_channel/parse_address.c). Connected sources describe it as a heap-based overflow that could impact availability, integrity, and confidentiality (NVD CVSS3...
CVE-2017-7861
Google gRPC before 2017-02-22 contains an out-of-bounds write in gpr_free (core/lib/support/alloc.c). Affected component is the gRPC core library; vulnerability arises from an out-of-bounds write in gpr_free. CVSS indicates high/critical impact with potential for crash or code execution depending...
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...
CVE-2017-7861
Google gRPC before 2017-02-22 has an out-of-bounds write related to the gprfree function in core/lib/support/alloc.c...