CVE-2020-15199Medium· 5.9▾ SunlitDenial of Service in Tensorflow
▾ Sunlit zone — Low / medium · no exploitation signal
impact 32.5 · likelihood 0.2 · 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.8%
0.8% → 0.8%
The RaggedCountSparseOutput does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the splits tensor has the minimum required number of elements. Code uses this quantity to initialize a different data structure:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L241-L244
Since BatchedMap is equivalent to a vector, it needs to have at least one element to not be nullptr. If user passes a splits tensor that is empty or has exactly one element, we get a SIGABRT signal raised by the operating system.
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 is a variant of GHSA-p5f8-gfw5-33w4
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-15197Medium· 6.3Denial of Service in Tensorflow
CVE-2020-15196High· 8.5Heap buffer overflow in Tensorflow
CVE-2020-15201Medium· 4.8Heap buffer overflow in Tensorflow
CVE-2020-15207High· 8.7Segfault and data corruption in tensorflow-lite