CVE-2021-41220 Use after free in `CollectiveReduceV2`
An attacker can trigger a use-after-free in TensorFlow's CollectiveReduceV2, potentially leading to code execution or denial of service.
- 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-41220?
CVE-2021-41220 is a high-severity use after free 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 async implementation of `CollectiveReduceV2` suffers from a memory leak and a use after free. This occurs due to the asynchronous computation and the fact that objects that have been `std::move()`d from are still accessed. 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-416
Which versions are affected by CVE-2021-41220?
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-41220?
Upgrade tensorflow to a fixed version for your release line: 2.6.1 or 2.7.0.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is CVE-2021-41220 being exploited?
There is no known exploitation of CVE-2021-41220 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-41220, GHSA-gpfh-jvf9-7wg5, PYSEC-2021-412, PYSEC-2021-629, PYSEC-2021-827.