CVE-2017-9431: Buffer Overflow
First published: Mon Jun 05 2017(Updated: )
Google gRPC before 2017-04-05 has an out-of-bounds write caused by a heap-based buffer overflow related to core/lib/iomgr/error.c.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| gRPC | <=1.2.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-9431?
CVE-2017-9431 is classified as a high-severity vulnerability due to the potential for an out-of-bounds write leading to a heap-based buffer overflow.
How do I fix CVE-2017-9431?
To fix CVE-2017-9431, upgrade gRPC to version 1.2.3 or later, as this version addresses the vulnerability.
What impact does CVE-2017-9431 have on gRPC applications?
CVE-2017-9431 can lead to crashes or arbitrary code execution in gRPC applications if exploited.
Is CVE-2017-9431 present in all versions of gRPC?
CVE-2017-9431 affects all versions of gRPC before 1.2.3.
What components are affected by CVE-2017-9431?
CVE-2017-9431 specifically affects the core library components related to error handling in gRPC.
- agent/references
- agent/type
- agent/last-modified-date
- agent/remedy
- agent/first-publish-date
- agent/severity
- agent/weakness
- agent/author
- agent/tags
- agent/softwarecombine
- agent/description
- agent/event
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/grpc
- canonical/grpc
- version/grpc/1.2.2