Integer overflows 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 `AddManySparseToTensorsMap` is vulnerable to an integer overflow which results in a `CHECK`-fail when building new `TensorShape` objects (so, an assert failure based denial of service). We are missing some validation on the shapes of the input tensors as well as directly constructing a large `TensorShape` with user-provided dimensions. 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
AddManySparseToTensorsMap does not adequately validate input tensor shapes. Processing tensors with attacker-controlled dimensions can trigger an integer overflow and assertion failure, causing a denial of service. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Check installations of PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu below 2.5.3, from 2.6.0 to below 2.6.3, or from 2.7.0 to below 2.7.1.