CVE-2020-15201Medium· 4.8▾ SunlitHeap buffer overflow in Tensorflow
▾ Sunlit zone — Low / medium · no exploitation signal
impact 26.4 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.6%
0.6% → 0.6%
The RaggedCountSparseOutput implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the splits tensor generate a valid partitioning of the values tensor. Hence, this code is prone to heap buffer overflow:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L248-L251
If split_values does not end with a value at least num_values then the while loop condition will trigger a read outside of the bounds of split_values once batch_idx grows too large.
We have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.
We recommend users to upgrade to TensorFlow 2.3.1.
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
tensorflow >= 2.3.0, < 2.3.1tensorflow-cpu >= 2.3.0, < 2.3.1tensorflow-gpu >= 2.3.0, < 2.3.1Upgrade to a patched release:
tensorflow 2.3.1tensorflow-cpu 2.3.1tensorflow-gpu 2.3.1Connected by shared product, vendor, weakness, or advisory.
CVE-2020-15198Medium· 5.4Heap buffer overflow in Tensorflow
CVE-2020-15200Medium· 5.9Segfault in Tensorflow
CVE-2020-15199Medium· 5.9Denial of Service in Tensorflow
CVE-2020-15197Medium· 6.3Denial of Service in Tensorflow
CVE-2020-15196High· 8.5Heap buffer overflow in Tensorflow
CVE-2020-15207High· 8.7Segfault and data corruption in tensorflow-lite