CVE-2019-16778: low-severity vulnerability in tensorflow
Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
8Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 2.6epss 0.8%
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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
Affected products
tensorflow · tensorflowRelated CVEs — tensorflow
In the same product, most dangerous first.
CVE-2020-15202CRITICALInteger truncation in Shard API usageEPSS 1.3%CVE-2020-15207HIGHSegfault and data corruption in tensorflow-liteEPSS 1.2%CVE-2022-23559HIGHInteger overflow in TFLiteEPSS 1.2%CVE-2022-23581MEDIUM`CHECK`-failures during Grappler's `IsSimplifiableReshape` in TensorflowEPSS 1.2%CVE-2022-23589MEDIUMNull pointer dereference in Grappler's `IsConstant` in TensorflowEPSS 1.1%CVE-2020-15205CRITICALData leak in TensorflowEPSS 1.0%