CVE-2017-8359: Use After Free
First published: Sun Apr 30 2017(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| gRPC | <=1.2.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-8359?
CVE-2017-8359 has been assigned a high severity score due to the potential for exploitation through out-of-bounds writes.
How do I fix CVE-2017-8359?
To fix CVE-2017-8359, update gRPC to version 1.2.2 or later.
What does the vulnerability CVE-2017-8359 affect?
CVE-2017-8359 affects the gRPC library versions up to and including 1.2.1.
Can CVE-2017-8359 lead to remote code execution?
Yes, exploitation of CVE-2017-8359 can potentially lead to remote code execution.
What is the cause of CVE-2017-8359?
CVE-2017-8359 is caused by a heap-based use-after-free vulnerability related to the grpc_call_destroy function.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/references
- agent/remedy
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/grpc
- canonical/grpc
- version/grpc/1.2.1