Advisory

PYSEC-2020-336

Also known as: BIT-tensorflow-2020-26270, CVE-2020-26270, GHSA-m648-33qf-v3gp, PYSEC-2020-256, PYSEC-2020-301

Summary

The record has no summary.

Details

In affected versions of TensorFlow running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a CHECK failure when using the CUDA backend. This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0.

Severity

Not rated by the source.

Dates

Published
2020-12-10 23:15 UTC
Modified
2023-12-06 01:00 UTC

Affected packages and fixes

tensorflow-gpu

PyPI · All systems

Affected

  • introduced 0, fixed 1.15.5, introduced 2.0.0, fixed 2.0.4, introduced 2.1.0, fixed 2.1.3, introduced 2.2.0, fixed 2.2.2, introduced 2.3.0, fixed 2.3.2 (ecosystem)

Fixed versions

1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2

Fix

  • Fixed version 1.15.5
    pip install --upgrade tensorflow-gpu==1.15.5
  • Fixed version 2.0.4
    pip install --upgrade tensorflow-gpu==2.0.4
  • Fixed version 2.1.3
    pip install --upgrade tensorflow-gpu==2.1.3
  • Fixed version 2.2.2
    pip install --upgrade tensorflow-gpu==2.2.2
  • Fixed version 2.3.2
    pip install --upgrade tensorflow-gpu==2.3.2

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