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.
Advisories
Source ID Title
EUVD EUVD EUVD-2019-0142 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.
Github GHSA Github GHSA GHSA-844w-j86r-4x2j Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2024-08-05T01:24:48.540Z

Reserved: 2019-09-24T00:00:00

Link: CVE-2019-16778

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2019-12-16T21:15:11.403

Modified: 2024-11-21T04:31:10.367

Link: CVE-2019-16778

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.