Incomplete validation of shapes in multiple TF ops
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
≥ 2.5.0 · < 2.5.2< 2.4.4
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an open source platform for machine learning. In affected versions several TensorFlow operations are missing validation for the shapes of the tensor arguments involved in the call. Depending on the API, this can result in undefined behavior and segfault or `CHECK`-fail related crashes but in some scenarios writes and reads from heap populated arrays are also possible. We have discovered these issues internally via tooling while working on improving/testing GPU op determinism. As such, we don't have reproducers and there will be multiple fixes for these issues. These fixes will be included in TensorFlow 2.7.0. We will also cherrypick these commits on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
From the CVE record · GitHub_M
Several TensorFlow operations do not validate tensor argument shapes. When given improperly shaped tensors, they can crash or, in some cases, read or write heap arrays. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Engineers using PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu versions >=2.6.0 and <2.6.1, >=2.5.0 and <2.5.2, or <2.4.4 should check their installations.