An attacker can cause undefined behavior via binding a reference to null pointer in tf.raw_ops.Map*
and tf.raw_ops.OrderedMap*
operations:
import tensorflow as tf
tf.raw_ops.MapPeek(
key=tf.constant([8],dtype=tf.int64),
indices=[],
dtypes=[tf.int32],
capacity=8,
memory_limit=128)
The implementation has a check in place to ensure that indices
is in ascending order, but does not check that indices
is not empty.
We have patched the issue in GitHub commit 532f5c5a547126c634fefd43bbad1dc6417678ac.
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.
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.