| Package | Affected versions | Patched versions |
|---|---|---|
| tensorflow | ≥ 2.0.0, < 2.0.4≥ 2.1.0, < 2.1.3≥ 2.2.0, < 2.2.2≥ 2.3.0, < 2.3.2< 1.15.5 | 2.0.42.1.32.2.22.3.21.15.5 |
| tensorflow-cpu | ≥ 2.0.0, < 2.0.4≥ 2.1.0, < 2.1.3≥ 2.2.0, < 2.2.2≥ 2.3.0, < 2.3.2< 1.15.5 | 2.0.42.1.32.2.22.3.21.15.5 |
| tensorflow-gpu | ≥ 2.0.0, < 2.0.4≥ 2.1.0, < 2.1.3≥ 2.2.0, < 2.2.2≥ 2.3.0, < 2.3.2< 1.15.5 | 2.0.42.1.32.2.22.3.21.15.5 |
| tensorflow | ≥ 2.0.0, < 2.0.4≥ 2.1.0, < 2.1.3≥ 2.2.0, < 2.2.2≥ 2.3.0, < 2.3.2< 1.15.5 | 2.0.42.1.32.2.22.3.21.15.5 |
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.
We have patched the issue in GitHub 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.
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free