← Back to results
Vulnerability record · public intelligence
CVE-2017-8359
CRITICAL

CVE-2017-8359

Published Apr 30, 2017 · Updated Oct 23, 2026 · Also known as PYSEC-2017-101

Severity · CVSSCRITICAL · 9.8
Known exploitationNot listed
EPSS / likelihood3.08%
QFinch risk score20 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

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.

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

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.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSS
SSVC priority
MEDIUM
Confidence
20%
Aliases
PYSEC-2017-101

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. bugs.chromium.org ↗
  2. 98280 ↗
  3. Source repository ↗

Record history

Published Apr 30, 2017 · Last refreshed Oct 23, 2026