Skip to content
Fencer Intel
low 2.6

CVE-2019-16778 json

Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow

published 6y ago modified 4mo ago also GHSA-844w-j86r-4x2j , PYSEC-2019-209 , PYSEC-2019-227 , PYSEC-2019-234 , EUVD-2019-0142

cvss
2.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and num_segments fields are truncated from int64 to int32 and can produce negative numbers, resulting in accessing out of bounds heap memory. This is unlikely to be exploitable and was detected and fixed internally in TensorFlow 1.15 and 2.0.

Patch / fix

  • pypi tensorflow 1.15.0
  • pypi tensorflow-cpu 1.15.0
  • pypi tensorflow-gpu 1.15.0
  • tensorflow tensorflow 1.15

Is CVE-2019-16778 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 2.6 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
NVD 3.1 9.8 CVSS:3.1/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
GitHub 3.1 2.6 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
pypi tensorflow
<1.15.0
>=1.0.0, <1.15.0
1.15.0
pypi tensorflow-cpu
<1.15.0
>=1.0.0, <1.15.0
1.15.0
pypi tensorflow-gpu
<1.15.0
>=1.0.0, <1.15.0
1.15.0

Affected products

  • tensorflow tensorflow

Classification

Weakness
  • CWE-122 Heap-based Buffer Overflow
  • CWE-681 Incorrect Conversion between Numeric Types

References

Sources

Fencer Intel 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.