CVE-2021-29607 Incomplete validation in `SparseSparseMinimum`
Attackers can trigger null pointer dereferences and heap overflows in TensorFlow's SparseAdd operation, potentially leading to code execution or crashes.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2021-29607?
CVE-2021-29607 is a medium-severity vulnerability in Google Tensorflow, published on 14 May 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. Incomplete validation in `SparseAdd` results in allowing attackers to exploit undefined behavior (dereferencing null pointers) as well as write outside of bounds of heap allocated data. The implementation(https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/sparse_sparse_binary_op_shared.cc) has a large set of validation for the two sparse tensor inputs (6 tensors in total), but does not validate that the tensors are not empty or that the second dimension of `*_indices` matches the size of corresponding `*_shape`. This allows attackers to send tensor triples that represent invalid sparse tensors to abuse code assumptions that are not protected by validation. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
Weakness: CWE-754
Which versions are affected by CVE-2021-29607?
28 open source packages ship an affected version, including tensorflow, tensorflow-cpu and tensorflow-gpu. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
tensorflow Bitnami | All versions | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
tensorflow PyPI | All versions | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
tensorflow PyPI | All versions | 2.1.4 |
tensorflow PyPI | All versions | 2.1.4 |
tensorflow PyPI | From 2.2.0 | 2.2.3 |
tensorflow PyPI | From 2.2.0 | 2.2.3 |
22 more packages
tensorflow PyPI | From 2.3.0 | 2.3.3 |
tensorflow PyPI | From 2.3.0 | 2.3.3 |
tensorflow PyPI | From 2.4.0 | 2.4.2 |
tensorflow PyPI | From 2.4.0 | 2.4.2 |
tensorflow-cpu PyPI | All versions | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
tensorflow-cpu PyPI | All versions | 2.1.4 |
tensorflow-cpu PyPI | All versions | 2.1.4 |
tensorflow-cpu PyPI | From 2.2.0 | 2.2.3 |
tensorflow-cpu PyPI | From 2.2.0 | 2.2.3 |
tensorflow-cpu PyPI | From 2.3.0 | 2.3.3 |
tensorflow-cpu PyPI | From 2.3.0 | 2.3.3 |
tensorflow-cpu PyPI | From 2.4.0 | 2.4.2 |
tensorflow-cpu PyPI | From 2.4.0 | 2.4.2 |
tensorflow-gpu PyPI | All versions | 2.1.4, 2.2.3, 2.3.3, 2.4.2 |
tensorflow-gpu PyPI | All versions | 2.1.4 |
tensorflow-gpu PyPI | All versions | 2.1.4 |
tensorflow-gpu PyPI | From 2.2.0 | 2.2.3 |
tensorflow-gpu PyPI | From 2.2.0 | 2.2.3 |
tensorflow-gpu PyPI | From 2.3.0 | 2.3.3 |
tensorflow-gpu PyPI | From 2.3.0 | 2.3.3 |
tensorflow-gpu PyPI | From 2.4.0 | 2.4.2 |
tensorflow-gpu PyPI | From 2.4.0 | 2.4.2 |
Products include Google Tensorflow.
How do I fix CVE-2021-29607?
Upgrade tensorflow to a fixed version for your release line: 2.1.4, 2.2.3, 2.3.3 or 2.4.2.
Is CVE-2021-29607 being exploited?
There is no known exploitation of CVE-2021-29607 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
- CVE-2018-7575 Integer Overflow or Wraparound in Google TensorFlow
- CVE-2021-37678 Arbitrary code execution due to YAML deserialization
- CVE-2021-35958 Path traversal in n/a
- CVE-2020-15202 Integer truncation in Shard API usage
Sources
Also known as BIT-tensorflow-2021-29607, GHSA-gv26-jpj9-c8gq, PYSEC-2021-244, PYSEC-2021-535, PYSEC-2021-733.