CVE-2017-7860: Buffer Overflow
First published: Fri Apr 14 2017(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| gRPC | <=1.1.2 |
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-7860?
CVE-2017-7860 has been classified as a high severity vulnerability due to its potential to cause a heap-based buffer overflow.
How do I fix CVE-2017-7860?
To fix CVE-2017-7860, update gRPC to version 1.1.3 or later, which addresses the vulnerability.
What software is affected by CVE-2017-7860?
CVE-2017-7860 affects all versions of gRPC prior to version 1.1.3.
What type of vulnerability is CVE-2017-7860?
CVE-2017-7860 is an out-of-bounds write vulnerability caused by a heap-based buffer overflow.
Which function is responsible for CVE-2017-7860?
The vulnerability is related to the parse_unix function in the file core/ext/client_channel/parse_address.c.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/last-modified-date
- agent/remedy
- agent/severity
- agent/weakness
- agent/references
- agent/description
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/grpc
- canonical/grpc
- version/grpc/1.1.2