CVE-2021-29544 CHECK-fail in `QuantizeAndDequantizeV4Grad`
An attacker can cause a denial of service in TensorFlow by triggering a CHECK-fail in QuantizeAndDequantizeV4Grad due to missing tensor rank validation.
- 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-29544?
CVE-2021-29544 is a low-severity denial of service 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. An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.QuantizeAndDequantizeV4Grad`. This is because the implementation does not validate the rank of the `input_*` tensors. In turn, this results in the tensors being passes as they are to `QuantizeAndDequantizePerChannelGradientImpl`. However, the `vec<T>` method, requires the rank to 1 and triggers a `CHECK` failure otherwise. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 as this is the only other affected version.
Weakness: CWE-754
Which versions are affected by CVE-2021-29544?
10 open source packages ship an affected version, including tensorflow, tensorflow-cpu and tensorflow-gpu. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
tensorflow Bitnami | From 2.4.0 | 2.4.2 |
tensorflow PyPI | All versions | 2.2.0rc0, 2.3.0rc0, 2.3.4, 2.4.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.2.0rc0, 2.3.0rc0, 2.3.4, 2.4.3 |
tensorflow-cpu PyPI | From 2.4.0 | 2.4.2 |
4 more packages
tensorflow-cpu PyPI | From 2.4.0 | 2.4.2 |
tensorflow-gpu PyPI | All versions | 2.2.0rc0, 2.3.0rc0, 2.3.4, 2.4.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-29544?
Upgrade tensorflow to a fixed version for your release line: 2.4.2, 2.2.0rc0, 2.3.0rc0 or 2.3.4.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2021-29544 being exploited?
There is no known exploitation of CVE-2021-29544 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-29544, GHSA-6g85-3hm8-83f9, PYSEC-2021-181, PYSEC-2021-472, PYSEC-2021-670.