| Package | Affected versions | Patched versions |
|---|---|---|
| tensorflow | ≥ 2.6.0, < 2.6.3≥ 2.7.0, < 2.7.1< 2.5.3 | 2.6.32.7.12.5.3 |
| tensorflow-cpu | ≥ 2.6.0, < 2.6.3≥ 2.7.0, < 2.7.1< 2.5.3 | 2.6.32.7.12.5.3 |
| tensorflow-gpu | ≥ 2.6.0, < 2.6.3≥ 2.7.0, < 2.7.1< 2.5.3 | 2.6.32.7.12.5.3 |
| tensorflow | = 2.7.0≥ 2.6.0, ≤ 2.6.2≤ 2.5.2 |
When decoding a tensor from protobuf, a TensorFlow process can encounter cases where a CHECK assertion is invalidated based on user controlled arguments, if the tensors have an invalid dtype and 0 elements or an invalid shape. This allows attackers to cause denial of services in TensorFlow processes.
We have patched the issue in GitHub commit 5b491cd5e41ad63735161cec9c2a568172c8b6a3.
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
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