Null-dereference 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. When decoding a tensor from protobuf, TensorFlow might do a null-dereference if attributes of some mutable arguments to some operations are missing from the proto. This is guarded by a `DCHECK`. However, `DCHECK` is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the dereferencing of the null pointer, whereas in the second case it results in a crash due to the assertion failure. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range.
From the CVE record · GitHub_M
TensorFlow can crash while decoding a tensor from protobuf if attributes of certain mutable operation arguments are missing. The missing attributes can cause a null-pointer dereference in production builds or an assertion failure in debug builds. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Teams running affected PyPI versions of tensorflow, tensorflow-cpu, or tensorflow-gpu—below 2.5.3, 2.6.0 through 2.6.2, or 2.7.0—should check their installations.