Segfault in Tensorflow

MEDIO 5.3CVE-2020-15190 · BIT-tensorflow-2020-15190 · GHSA-4g9f-63rx-5cw4 · Published 25/09/2020 · updated 17/06/2026

En resumen

CVE-2020-15190 es una vulnerabilidad MEDIO (CVSS 5.3) que afecta a tensorflow, tensorflow-cpu, tensorflow-gpu.
Probabilidad de explotación en los próximos 30 días (EPSS): 0.94%, mayor que el 61.3% de las vulnerabilidades.
Solución: actualizar a 2.0.3, 2.1.2, 2.2.1, 2.3.1 o posterior.

Package	Affected versions	Patched versions
tensorflow PyPI	`≥ 2.0.0, < 2.0.3≥ 2.1.0, < 2.1.2≥ 2.2.0, < 2.2.1≥ 2.3.0, < 2.3.1< 1.15.4`	`2.0.32.1.22.2.12.3.11.15.4`
tensorflow-cpu PyPI	`≥ 2.0.0, < 2.0.3≥ 2.1.0, < 2.1.2≥ 2.2.0, < 2.2.1≥ 2.3.0, < 2.3.1< 1.15.4`	`2.0.32.1.22.2.12.3.11.15.4`
tensorflow-gpu PyPI	`≥ 2.0.0, < 2.0.3≥ 2.1.0, < 2.1.2≥ 2.2.0, < 2.2.1≥ 2.3.0, < 2.3.1< 1.15.4`	`2.0.32.1.22.2.12.3.11.15.4`
tensorflow google	`≥ 2.0.0, < 2.0.3≥ 2.1.0, < 2.1.2≥ 2.2.0, < 2.2.1≥ 2.3.0, < 2.3.1< 1.15.4`	`2.0.32.1.22.2.12.3.11.15.4`

Description

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.

NVD description

In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, 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. 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 The issue is patched in commit da8558533d925694483d2c136a9220d6d49d843c, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.