Advisory

PYSEC-2020-270

Also known as: BIT-tensorflow-2020-15190, CVE-2020-15190, GHSA-4g9f-63rx-5cw4, PYSEC-2020-113, PYSEC-2020-305

Summary

The record has no summary.

Details

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.

Severity

Not rated by the source.

Dates

Published
2020-09-25 19:15 UTC
Modified
2023-12-06 01:00 UTC

Affected packages and fixes

tensorflow-cpu

PyPI · All systems

Affected

  • introduced 0, fixed 1.15.4, introduced 2.0.0, fixed 2.0.3, introduced 2.1.0, fixed 2.1.2, introduced 2.2.0, fixed 2.2.1, introduced 2.3.0, fixed 2.3.1 (ecosystem)

Fixed versions

1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1

Fix

  • Fixed version 1.15.4
    pip install --upgrade tensorflow-cpu==1.15.4
  • Fixed version 2.0.3
    pip install --upgrade tensorflow-cpu==2.0.3
  • Fixed version 2.1.2
    pip install --upgrade tensorflow-cpu==2.1.2
  • Fixed version 2.2.1
    pip install --upgrade tensorflow-cpu==2.2.1
  • Fixed version 2.3.1
    pip install --upgrade tensorflow-cpu==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: PyPA Advisory Database · CC BY 4.0

Sources & licences