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.
The product writes data past the end, or before the beginning, of the intended buffer.
Link | Tags |
---|---|
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=661 | vdb entry third party advisory |
http://www.securityfocus.com/bid/97695 | vdb entry third party advisory |
https://github.com/grpc/grpc/pull/9833 | third party advisory patch |