Advisory

PYSEC-2020-258

Also known as: BIT-tensorflow-2020-5215, CVE-2020-5215, GHSA-977j-xj7q-2jr9, PYSEC-2020-303, PYSEC-2020-338

Summary

The record has no summary.

Details

In TensorFlow before 1.15.2 and 2.0.1, converting a string (from Python) to a tf.float16 value results in a segmentation fault in eager mode as the format checks for this use case are only in the graph mode. This issue can lead to denial of service in inference/training where a malicious attacker can send a data point which contains a string instead of a tf.float16 value. Similar effects can be obtained by manipulating saved models and checkpoints whereby replacing a scalar tf.float16 value with a scalar string will trigger this issue due to automatic conversions. This can be easily reproduced by tf.constant("hello", tf.float16), if eager execution is enabled. This issue is patched in TensorFlow 1.15.1 and 2.0.1 with this vulnerability patched. TensorFlow 2.1.0 was released after we fixed the issue, thus it is not affected. Users are encouraged to switch to TensorFlow 1.15.1, 2.0.1 or 2.1.0.

Severity

Not rated by the source.

Dates

Published
2020-01-28 22:15 UTC
Modified
2023-12-06 01:00 UTC

Affected packages and fixes

tensorflow

PyPI · All systems

Affected

  • introduced 0, fixed 1.15.2, introduced 2.0.0, fixed 2.0.1 (ecosystem)

Fixed versions

1.15.2, 2.0.1

Fix

  • Fixed version 1.15.2
    pip install --upgrade tensorflow==1.15.2
  • Fixed version 2.0.1
    pip install --upgrade tensorflow==2.0.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