Advisory

GHSA-4g9f-63rx-5cw4

Also known as: BIT-tensorflow-2020-15190, CVE-2020-15190, PYSEC-2020-113, PYSEC-2020-270, PYSEC-2020-305

Summary

Segfault in Tensorflow

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2020-09-25 18:28 UTC
Modified
2026-07-08 06:27 UTC

Affected packages and fixes

15 affected packages; all PyPI · All systems
PackageAffectedFix
tensorflowEarlier versionspip install --upgrade tensorflow==1.15.4
tensorflowintroduced 2.0.0, fixed 2.0.3pip install --upgrade tensorflow==2.0.3
tensorflowintroduced 2.1.0, fixed 2.1.2pip install --upgrade tensorflow==2.1.2
tensorflowintroduced 2.2.0, fixed 2.2.1pip install --upgrade tensorflow==2.2.1
tensorflowintroduced 2.3.0, fixed 2.3.1pip install --upgrade tensorflow==2.3.1
tensorflow-cpuEarlier versionspip install --upgrade tensorflow-cpu==1.15.4
tensorflow-cpuintroduced 2.0.0, fixed 2.0.3pip install --upgrade tensorflow-cpu==2.0.3
tensorflow-cpuintroduced 2.1.0, fixed 2.1.2pip install --upgrade tensorflow-cpu==2.1.2
tensorflow-cpuintroduced 2.2.0, fixed 2.2.1pip install --upgrade tensorflow-cpu==2.2.1
tensorflow-cpuintroduced 2.3.0, fixed 2.3.1pip install --upgrade tensorflow-cpu==2.3.1
tensorflow-gpuEarlier versionspip install --upgrade tensorflow-gpu==1.15.4
tensorflow-gpuintroduced 2.0.0, fixed 2.0.3pip install --upgrade tensorflow-gpu==2.0.3
tensorflow-gpuintroduced 2.1.0, fixed 2.1.2pip install --upgrade tensorflow-gpu==2.1.2
tensorflow-gpuintroduced 2.2.0, fixed 2.2.1pip install --upgrade tensorflow-gpu==2.2.1
tensorflow-gpuintroduced 2.3.0, fixed 2.3.1pip install --upgrade tensorflow-gpu==2.3.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences