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.
{
"extracted_events": [
{
"introduced": "0"
},
{
"last_affected": "1.2.1"
}
],
"source": "CPE_FIELD",
"cpe": "cpe:2.3:a:grpc:grpc:*:*:*:*:*:*:*:*"
}{
"extracted_events": [
{
"introduced": "0"
},
{
"last_affected": "1.2.1"
}
],
"source": "CPE_FIELD",
"cpe": "cpe:2.3:a:grpc:grpc:*:*:*:*:*:*:*:*"
}{
"extracted_events": [
{
"introduced": "0"
},
{
"last_affected": "1.2.1"
}
],
"source": "CPE_FIELD",
"cpe": "cpe:2.3:a:grpc:grpc:*:*:*:*:*:*:*:*"
}{
"extracted_events": [
{
"introduced": "0"
},
{
"last_affected": "1.2.1"
}
],
"source": "CPE_FIELD",
"cpe": "cpe:2.3:a:grpc:grpc:*:*:*:*:*:*:*:*"
}{
"extracted_events": [
{
"introduced": "0"
},
{
"last_affected": "1.2.1"
}
],
"source": "CPE_FIELD",
"cpe": "cpe:2.3:a:grpc:grpc:*:*:*:*:*:*:*:*"
}