CVE-2017-7861
CriticalSummary
Google gRPC before 2017-02-22 has an out-of-bounds write related to the gpr_free function in core/lib/support/alloc.c.
Risk Assessment
Exploitation of this vulnerability may lead to unexpected application behavior, potentially compromising system integrity.
Recommendation
It is recommended to update Google gRPC to a version after February 22, 2017, to mitigate this vulnerability.
Other vulnerabilities in Google gRPC
See all- CVE-2017-9431Critical
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.
- CVE-2017-8359Critical
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.
- CVE-2017-7860Critical
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.
Original NVD description (English source)
Google gRPC before 2017-02-22 has an out-of-bounds write related to the gpr_free function in core/lib/support/alloc.c.