CVE-2017-8359 json
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…
published 2017-04-30 9 y ago modified 2026-06-17 4 mo ago also PYSEC-2017-101 , EUVD-2017-0058
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi grpcio 1.3.0
- grpc Debian 14, Debian 13, Debian 12 1.3.2-0.1
debian advisories DEBIAN-CVE-2017-8359
- github.com/grpc/grpc@6544a2d commit
- github.com/grpc/grpc#10353 pull request
Exploit prediction
3.08% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- bugs.chromium.org https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=726 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | grpcio | <1.3.0 |
1.3.0 |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
github.com
/grpc/grpc/pull/10353
patch, third-party-advisory, web
-
github.com
/grpc/grpc/commit/6544a2d5d9ecdb64214da1d228886a7d15bbf5c7
patch
-
bugs.chromium.org
/p/oss-fuzz/issues/detail?id=726
exploit, third-party-advisory, web
-
securityfocus.com
/bid/98280
vdb-entry, third-party-advisory, web
-
pypi.org
/project/grpcio
package
-
nvd.nist.gov
/vuln/detail/CVE-2017-8359
advisory
Sources
- CVE List CVE-2017-8359
- NVD CVE-2017-8359
- OSV PYSEC-2017-101
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.