GHSA-4g9f-63rx-5cw4 Segfault in Tensorflow

• PyPI tensorflow: < 1.15.4 → fixed in 1.15.4 • PyPI tensorflow: >= 2.0.0, < 2.0.3 → fixed in 2.0.3 • PyPI tensorflow: >= 2.1.0, < 2.1.2 → fixed in 2.1.2 • PyPI tensorflow: >= 2.2.0, < 2.2.1 → fixed in 2.2.1 • PyPI tensorflow: >= 2.3.0, < 2.3.1 → fixed in 2.3.1 • PyPI tensorflow-cpu: < 1.15.4 → fixed in 1.15.4 • PyPI tensorflow-cpu: >= 2.0.0, < 2.0.3 → fixed in 2.0.3 • PyPI tensorflow-cpu: >= 2.1.0, < 2.1.2 → fixed in 2.1.2 • PyPI tensorflow-cpu: >= 2.2.0, < 2.2.1 → fixed in 2.2.1 • PyPI tensorflow-cpu: >= 2.3.0, < 2.3.1 → fixed in 2.3.1 • PyPI tensorflow-gpu: < 1.15.4 → fixed in 1.15.4 • PyPI tensorflow-gpu: >= 2.0.0, < 2.0.3 → fixed in 2.0.3 • PyPI tensorflow-gpu: >= 2.1.0, < 2.1.2 → fixed in 2.1.2 • PyPI tensorflow-gpu: >= 2.2.0, < 2.2.1 → fixed in 2.2.1 • PyPI tensorflow-gpu: >= 2.3.0, < 2.3.1 → fixed in 2.3.1

Impact The `tf.raw_ops.Switch` operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. However, the eager runtime traverses all tensors in the output: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/common_runtime/eager/kernel_and_device.cc#L308-L313 Since only one of the tensors is defined, the other one is `nullptr`, hence we are binding a reference to `nullptr`. This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. In this case, this results in a segmentation fault Patches We have patched the issue in da8558533d925694483d2c136a9220d6d49d843c and will release a patch release for all affected versions. We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. 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.