Advisory

PYSEC-2020-317

Also known as: BIT-tensorflow-2020-15202, CVE-2020-15202, GHSA-h6fg-mjxg-hqq4, PYSEC-2020-125, PYSEC-2020-282

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 Shard API in TensorFlow expects the last argument to be a function taking two int64 (i.e., long long) arguments. However, there are several places in TensorFlow where a lambda taking int or int32 arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption. The issue is patched in commits 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575, 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-gpu

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

Sources & licences