CVE-2021-29582 Heap OOB read in `tf.raw_ops.Dequantize`
An attacker can trigger an out-of-bounds heap read in TensorFlow's Dequantize operation due to missing shape validation, potentially causing crashes or data exposure.
- 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-29582?
CVE-2021-29582 is a low-severity memory corruption 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. Due to lack of validation in `tf.raw_ops.Dequantize`, an attacker can trigger a read from outside of bounds of heap allocated data. The implementation(https://github.com/tensorflow/tensorflow/blob/26003593aa94b1742f34dc22ce88a1e17776a67d/tensorflow/core/kernels/dequantize_op.cc#L106-L131) accesses the `min_range` and `max_range` tensors in parallel but fails to check that they have the same shape. 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-125
Which versions are affected by CVE-2021-29582?
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-29582?
Upgrade tensorflow to a fixed version for your release line: 2.1.4, 2.2.3, 2.3.3 or 2.4.2.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2021-29582 being exploited?
There is no known exploitation of CVE-2021-29582 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-29582, GHSA-c45w-2wxr-pp53, PYSEC-2021-219, PYSEC-2021-510, PYSEC-2021-708.