CVE-2017-8359: PYSEC-2017-101 - Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free…

CVE-2017-8359 · Severity: info · Published 2017-04-30

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.

Technologies: grpcio (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2017-8359 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2017-8359 being exploited in the wild.
How severe is CVE-2017-8359?
Informational severity, published 30 April 2017.
Which products and versions are affected?
grpcio (PyPI) GIT:introduced=0,fixed=6544a2d5d9ecdb64214da1d228886a7d15bbf5c7|ECOSYSTEM:introduced=0,fixed=1.3.0.
Is there a fix for CVE-2017-8359?
Yes. grpcio (PyPI): upgrade to 1.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2017-8359?
Check whether you run grpcio (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • grpcio (PyPI): upgrade to 1.3.0 or later
    pip install "grpcio>=1.3.0"

Affected products

  • grpcio (PyPI) GIT:introduced=0,fixed=6544a2d5d9ecdb64214da1d228886a7d15bbf5c7|ECOSYSTEM:introduced=0,fixed=1.3.0

Identifiers

  • CVE-2017-8359
  • PYSEC-2017-101

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.