CVE-2021-41211 Heap OOB read in shape inference for `QuantizeV2`
An attacker can trigger a heap out-of-bounds read in TensorFlow's QuantizeV2 shape inference by providing a negative axis value, potentially leaking memory or causing a crash.
- 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-41211?
CVE-2021-41211 is a high-severity memory corruption vulnerability in Google Tensorflow, published on 5 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
TensorFlow is an open source platform for machine learning. In affected versions the shape inference code for `QuantizeV2` can trigger a read outside of bounds of heap allocated array. This occurs whenever `axis` is a negative value less than `-1`. In this case, we are accessing data before the start of a heap buffer. The code allows `axis` to be an optional argument (`s` would contain an `error::NOT_FOUND` error code). Otherwise, it assumes that `axis` is a valid index into the dimensions of the `input` tensor. If `axis` is less than `-1` then this results in a heap OOB read. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected.
Weakness: CWE-125
Which versions are affected by CVE-2021-41211?
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.6.0 | 2.6.1 |
tensorflow PyPI | From 2.6.0 | 2.6.1, 2.7.0 |
tensorflow PyPI | From 2.6.0 | 2.6.1 |
tensorflow PyPI | From 2.6.0 | 2.6.1 |
tensorflow-cpu PyPI | From 2.6.0 | 2.6.1, 2.7.0 |
tensorflow-cpu PyPI | From 2.6.0 | 2.6.1 |
4 more packages
tensorflow-cpu PyPI | From 2.6.0 | 2.6.1 |
tensorflow-gpu PyPI | From 2.6.0 | 2.6.1, 2.7.0 |
tensorflow-gpu PyPI | From 2.6.0 | 2.6.1 |
tensorflow-gpu PyPI | From 2.6.0 | 2.6.1 |
Products include Google Tensorflow.
How do I fix CVE-2021-41211?
Upgrade tensorflow to a fixed version for your release line: 2.6.1 or 2.7.0.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2021-41211 being exploited?
There is no known exploitation of CVE-2021-41211 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-41211, GHSA-cvgx-3v3q-m36c, PYSEC-2021-403, PYSEC-2021-620, PYSEC-2021-818.