CVE-2022-23583

Medium

Description

Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that any binary op would trigger `CHECK` failures. This occurs when the protobuf part corresponding to the tensor arguments is modified such that the `dtype` no longer matches the `dtype` expected by the op. In that case, calling the templated binary operator for the binary op would receive corrupted data, due to the type confusion involved. If `Tin` and `Tout` don't match the type of data in `out` and `input_*` tensors then `flat<*>` would interpret it wrongly. In most cases, this would be a silent failure, but we have noticed scenarios where this results in a `CHECK` crash, hence a denial of service. 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.

SeverityMedium
CVSS6.5
Exploit probability—
ProductGoogle Tensorflow
PublishedFeb 4, 2022
First seenFeb 4, 2022
Weakness typeCWE-617CWE-617

How to fix

Update
  • 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

ProductAffected versionsFixed in
google tensorflowv ≤ 2.5.2, 2.6.0 ≤ v ≤ 2.6.2, 2.7.0—
tensorflowPyPIv < 2.5.3, 2.6.0 ≤ v < 2.6.3, 2.7.0 ≤ v < 2.7.12.5.3, 2.6.3, 2.7.1
tensorflow-cpuPyPIv < 2.5.3, 2.6.0 ≤ v < 2.6.3, 2.7.0 ≤ v < 2.7.12.5.3, 2.6.3, 2.7.1
tensorflow-gpuPyPIv < 2.5.3, 2.6.0 ≤ v < 2.6.3, 2.7.0 ≤ v < 2.7.12.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.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.