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.Referenceshttps://bugs.chromium.org/p/oss-fuzz/issues/detail?id=726http://www.securityfocus.com/bid/98280https://github.com/grpc/grpc/pull/10353
