| Package | Affected versions | Patched versions |
|---|---|---|
| tensorflow | ≥ 2.7.0, < 2.7.2≥ 2.8.0, < 2.8.1< 2.6.4 | 2.7.22.8.12.6.4 |
| tensorflow-cpu | ≥ 2.7.0, < 2.7.2≥ 2.8.0, < 2.8.1< 2.6.4 | 2.7.22.8.12.6.4 |
| tensorflow-gpu | ≥ 2.7.0, < 2.7.2≥ 2.8.0, < 2.8.1< 2.6.4 | 2.7.22.8.12.6.4 |
| tensorflow | = 2.7.0= 2.8.0= 2.9.0≥ 2.7.0, < 2.7.2< 2.6.4 | 2.7.22.6.4 |
There is a potential for segfault / denial of service in TensorFlow by calling tf.compat.v1.* ops which don't yet have support for quantized types (added after migration to TF 2.x):
import numpy as np
import tensorflow as tf
tf.compat.v1.placeholder_with_default(input=np.array([2]),shape=tf.constant(dtype=tf.qint8, value=np.array([1])))
In these scenarios, since the kernel is missing, a nullptr value is passed to ParseDimensionValue for the py_value argument. Then, this is dereferenced, resulting in segfault.
We have patched the issue in GitHub commit 237822b59fc504dda2c564787f5d3ad9c4aa62d9.
The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.4, 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.
This vulnerability has been reported by Hong Jin from Singapore Management University.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free