GHSA-4xfp-4pfp-89wg Reference binding to nullptr in `RaggedTensorToSparse`

• PyPI tensorflow: < 2.3.4 → fixed in 2.3.4 • PyPI tensorflow: >= 2.4.0, < 2.4.3 → fixed in 2.4.3 • PyPI tensorflow: >= 2.5.0, < 2.5.1 → fixed in 2.5.1 • PyPI tensorflow-cpu: < 2.3.4 → fixed in 2.3.4 • PyPI tensorflow-cpu: >= 2.4.0, < 2.4.3 → fixed in 2.4.3 • PyPI tensorflow-cpu: >= 2.5.0, < 2.5.1 → fixed in 2.5.1 • PyPI tensorflow-gpu: < 2.3.4 → fixed in 2.3.4 • PyPI tensorflow-gpu: >= 2.4.0, < 2.4.3 → fixed in 2.4.3 • PyPI tensorflow-gpu: >= 2.5.0, < 2.5.1 → fixed in 2.5.1

Impact An attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.RaggedTensorToSparse`: ```python import tensorflow as tf tf.raw_ops.RaggedTensorToSparse( rt_nested_splits=[[0, 38, 0]], rt_dense_values=[]) ``` The implementation has an incomplete validation of the splits values: it does not check that they are in increasing order. Patches We have patched the issue in GitHub commit 1071f554dbd09f7e101324d366eec5f4fe5a3ece. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. For more information Please consult our security guide for more information regarding the security model and how to contact us with issues and questions. Attribution This vulnerability has been reported by members of the Aivul Team from Qihoo 360.