CVE-2021-37639 Null pointer dereference and heap OOB read in TensorFlow

What is CVE-2021-37639?

CVE-2021-37639 is a high-severity vulnerability in Google Tensorflow, published on 12 Aug 2021. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

TensorFlow is an end-to-end open source platform for machine learning. When restoring tensors via raw APIs, if the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer. Alternatively, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration. The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/save_restore_tensor.cc#L158-L159) retrieves the tensor list corresponding to the `tensor_name` user controlled input and immediately retrieves the tensor at the restoration index (controlled via `preferred_shard` argument). This occurs without validating that the provided list has enough values. If the list is empty this results in dereferencing a null pointer (undefined behavior). If, however, the list has some elements, if the restoration index is outside the bounds this results in heap OOB read. We have patched the issue in GitHub commit 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

Weakness: CWE-125, CWE-476

Which versions are affected by CVE-2021-37639?

22 open source packages ship an affected version, including tensorflow, tensorflow-cpu and tensorflow-gpu. It affects 1 product.

Products include Google Tensorflow.

How do I fix CVE-2021-37639?

Upgrade tensorflow to a fixed version for your release line: 2.3.4, 2.4.3 or 2.5.1.

Is CVE-2021-37639 being exploited?

There is no known exploitation of CVE-2021-37639 in the wild and no public exploit code.

Other vulnerabilities in Google Tensorflow

• CVE-2023-25668 TensorFlow vulnerable to heap out-of-buffer read in the QuantizeAndDequantize operation Critical 9.8
• CVE-2018-7575 Integer Overflow or Wraparound in Google TensorFlow Critical 9.8
• CVE-2021-37678 Arbitrary code execution due to YAML deserialization Critical 9.3
• CVE-2021-35958 Path traversal in n/a Critical 9.1
• CVE-2020-15202 Integer truncation in Shard API usage Critical 9.0

All Google Tensorflow vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as BIT-tensorflow-2021-37639, GHSA-gh6x-4whr-2qv4, PYSEC-2021-261, PYSEC-2021-552, PYSEC-2021-750.