Uninitialized variable access in Tensorflow
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
≥ 2.6.0 · < 2.6.3≥ 2.7.0 · < 2.7.1
|
| tensorflow-gpu PyPI |
|
|
Tensorflow is an Open Source Machine Learning Framework. The implementation of `AssignOp` can result in copying uninitialized 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. 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.
From the CVE record · GitHub_M
TensorFlow’s AssignOp can copy uninitialized data into a new tensor because it does not check whether the right-hand side is initialized. This can cause undefined behavior. The input does not specify how an attacker could trigger it, whether authentication is needed, or whether user interaction is required.
Check installations of the PyPI packages tensorflow, tensorflow-cpu, and tensorflow-gpu in versions below 2.5.3, from 2.6.0 to below 2.6.3, or from 2.7.0 to below 2.7.1.