| 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 |
The implementation of AssignOp can result in copying unitialized data to a new tensor. This later results in undefined behavior.
The implementation has a check that the left hand side of the assignment is initialized (to minimize number of allocations), but does not check that the right hand side is also initialized.
We have patched the issue in GitHub commit ef1d027be116f25e25bb94a60da491c2cf55bd0b.
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