Type confusion during tensor casts lead to dereferencing null pointers
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
2.1.42.2.32.3.32.4.22.2.0rc02.3.0rc02.3.42.4.3| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an end-to-end open source platform for machine learning. Calling TF operations with tensors of non-numeric types when the operations expect numeric tensors result in null pointer dereferences. The conversion from Python array to C++ array(https://github.com/tensorflow/tensorflow/blob/ff70c47a396ef1e3cb73c90513da4f5cb71bebba/tensorflow/python/lib/core/ndarray_tensor.cc#L113-L169) is vulnerable to a type confusion. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
From the CVE record · GitHub_M
TensorFlow operations that expect numeric tensors can hit a null pointer dereference when given tensors of non-numeric types. The underlying Python-to-C++ array conversion has a type confusion vulnerability. The input does not specify an attacker access requirement or whether user interaction is needed.
Teams using affected versions of the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages should check their installations.