CVE-2017-7860
UnknownEPSS 3.13%
Last modified
CVE-2017-7860 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 3.13% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Grpc | Grpc | <= 1.1.2 |
References
- http://www.securityfocus.com/bid/97695Third Party Advisory, VDB Entry
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=661Third Party Advisory, VDB Entry
- https://github.com/grpc/grpc/pull/9833Patch, Third Party Advisory
- http://www.securityfocus.com/bid/97695Third Party Advisory, VDB Entry
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=661Third Party Advisory, VDB Entry
- https://github.com/grpc/grpc/pull/9833Patch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-7860?
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.
How severe is CVE-2017-7860?
Severity scoring for CVE-2017-7860 is pending analysis. The EPSS model estimates a 3.13% probability of exploitation in the next 30 days.
How do I fix CVE-2017-7860?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2017-7860?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST