~ / search / GHSA-m648-33qf-v3gp

GHSA-m648-33qf-v3gp

CHECK-fail in LSTM with zero-length input in TensorFlow

Source: GitHub Advisory Database (reviewed) Moderate CVE-2020-26270

Packages

EcosystemPackageAffectedFixed in
PyPI tensorflow < 1.15.5 1.15.5
PyPI tensorflow >= 2.0.0, < 2.0.4 2.0.4
PyPI tensorflow >= 2.1.0, < 2.1.3 2.1.3
PyPI tensorflow >= 2.2.0, < 2.2.2 2.2.2
PyPI tensorflow >= 2.3.0, < 2.3.2 2.3.2
PyPI tensorflow-cpu < 1.15.5 1.15.5
PyPI tensorflow-cpu >= 2.0.0, < 2.0.4 2.0.4
PyPI tensorflow-cpu >= 2.1.0, < 2.1.3 2.1.3
PyPI tensorflow-cpu >= 2.2.0, < 2.2.2 2.2.2
PyPI tensorflow-cpu >= 2.3.0, < 2.3.2 2.3.2
PyPI tensorflow-gpu < 1.15.5 1.15.5
PyPI tensorflow-gpu >= 2.0.0, < 2.0.4 2.0.4
PyPI tensorflow-gpu >= 2.1.0, < 2.1.3 2.1.3
PyPI tensorflow-gpu >= 2.2.0, < 2.2.2 2.2.2
PyPI tensorflow-gpu >= 2.3.0, < 2.3.2 2.3.2

Details

As written in the advisory (Markdown source, shown as plain text).

### Impact 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. ### Patches We have patched the issue in GitHub commit [14755416e364f17fb1870882fa778c7fec7f16e3](https://github.com/tensorflow/tensorflow/commit/14755416e364f17fb1870882fa778c7fec7f16e3) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved. Since this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.

References

External links from the advisory. They lead to third-party sites.