Memory exhaustion in Tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
| 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 `ThreadPoolHandle` can be used to trigger a denial of service attack by allocating too much memory. This is because the `num_threads` argument is only checked to not be negative, but there is no upper bound on its value. 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 ThreadPoolHandle checks that num_threads is nonnegative but does not enforce an upper bound. An attacker who can supply an excessively large value can cause excessive memory allocation and a denial of service. The input does not specify whether this requires network access, authentication, or user interaction.
Anyone using the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages 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 should check their installations.