CVE-2019-16778GHSA-844W-J86R-4X2JPYSEC-2019-209PYSEC-2019-227PYSEC-2019-234
Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.15, 1.15.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Timeline
- CVE published
- Record last updated
Affected versions
- tensorflow tensorflow
fixed in 1.15
- tensorflowPyPI
fixed in 1.15.0
- tensorflow-cpuPyPI
fixed in 1.15.0
- tensorflow-gpuPyPI
fixed in 1.15.0
- tensorflow-cpuPyPI
From 1.0.0 · fixed in 1.15.0
- tensorflowPyPI
From 1.0.0 · fixed in 1.15.0
- tensorflow-gpuPyPI
From 1.0.0 · fixed in 1.15.0