CVE-2022-23589
Description
Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow can trigger a null pointer dereference. There are 2 places where this can occur, for the same malicious alteration of a `SavedModel` file (fixing the first one would trigger the same dereference in the second place). First, during constant folding, the `GraphDef` might not have the required nodes for the binary operation. If a node is missing, the correposning `mul_*child` would be null, and the dereference in the subsequent line would be incorrect. We have a similar issue during `IsIdentityConsumingSwitch`. 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.
How to fix
- tensorflow2.5.3, 2.6.3, 2.7.1 or later
- tensorflow-cpu2.5.3, 2.6.3, 2.7.1 or later
- tensorflow-gpu2.5.3, 2.6.3, 2.7.1 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| google tensorflow | v ≤ 2.5.2, 2.6.0 ≤ v ≤ 2.6.2, 2.7.0 | — |
| tensorflowPyPI | v < 2.5.3, 2.6.0 ≤ v < 2.6.3, 2.7.0 ≤ v < 2.7.1 | 2.5.3, 2.6.3, 2.7.1 |
| tensorflow-cpuPyPI | v < 2.5.3, 2.6.0 ≤ v < 2.6.3, 2.7.0 ≤ v < 2.7.1 | 2.5.3, 2.6.3, 2.7.1 |
| tensorflow-gpuPyPI | v < 2.5.3, 2.6.0 ≤ v < 2.6.3, 2.7.0 ≤ v < 2.7.1 | 2.5.3, 2.6.3, 2.7.1 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.